BIZTRAC BETA
Rental and leasing of cars and light motor vehicles

BLINDHEIM AS

Org. no. 918084215 Limited company (AS) Giske Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.6m
Operating profit NOK 1.3m
Equity NOK 3.9m
Incorporated 2016
Share capital NOK 480,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BLINDHEIM AS is registered as a limited company in Giske, Møre og Romsdal with organisation number 918084215. The business is classified under rental and leasing of cars and light motor vehicles (NACE 77.110). The company was incorporated in 2016. Registered share capital is NOK 480,000, divided into 30000 shares. The company's stated purpose is: “Eie, utvikling, drift, utleie, kjøp og salg av fast eiendom, og annet som naturlig hører inn under dette, samt investeringer i og deltakelse i annen næringsvirksomhet med økonomisk formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.6m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.6m
Operating profit
NOK 1.3m
Equity
NOK 3.9m
Est. value
NOK 4.5m

Financial health · 2024

Liquidity
1.64
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.4%
Good
Equity as a share of total capital

Who owns BLINDHEIM AS?

SKJONG AS
BLINDHEIM AS
NOK 1.6m rev. · NOK 1.3m profit

BLINDHEIM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

BLINDHEIM AS er morselskap for 5 datterselskaper:

Frequently asked questions about BLINDHEIM AS

Who owns BLINDHEIM AS?

SKJONG AS is the largest registered owner, with 100.0%.

What is the revenue of BLINDHEIM AS?

BLINDHEIM AS had revenue of NOK 1.6m in 2024.

Where is BLINDHEIM AS based?

BLINDHEIM AS has its business address in Vigra.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 15.06.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.