BIZTRAC BETA
Development of building projects

LEVELDÅSEN AS

Org. no. 913745256 Limited company (AS) Ål Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 6.2m
Operating profit NOK 301,000
Equity NOK −14.3m
Incorporated 2014
Share capital NOK 1.8m

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−14,3 mill kr).

LEVELDÅSEN AS is registered as a limited company in Ål, Buskerud with organisation number 913745256. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2014. Registered share capital is NOK 1.8m, divided into 1830845 shares. The company's stated purpose is: “Planlegging og utbygging av infrastruktur samt markedsføring og salg av hyttetomter innenfor Leveldåsen sameie. Selskapet kan også delta i andre eiendomsprosjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.2m in revenue and NOK 301,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.2m
Operating profit
NOK 301,000
Equity
NOK −14.3m
Est. value
NOK 3.8m

Financial health · 2024

Liquidity
30.54
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-87.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LEVELDÅSEN AS?

NILS MEDGARD
LEVELDÅSEN AS
NOK 6.2m rev. · NOK 301,000 profit

LEVELDÅSEN AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does LEVELDÅSEN AS own?

LEVELDÅSEN AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about LEVELDÅSEN AS

Who owns LEVELDÅSEN AS?

NILS MEDGARD is the largest registered owner, with 16.5%.

What is the revenue of LEVELDÅSEN AS?

LEVELDÅSEN AS had revenue of NOK 6.2m in 2024.

Where is LEVELDÅSEN AS based?

LEVELDÅSEN AS has its business address in Ål.

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.