BIZTRAC BETA
Uoppgitt

TOPP LEILIGHETER AS

Org. no. 920564208 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −9,000
Equity NOK −618,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−618k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−9k kr).

TOPP LEILIGHETER AS is registered as a limited company in Oslo, Oslo with organisation number 920564208. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Drive med kjøp og salg av leiligheter, eiendomsutvikling samt deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −9,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −9,000
Equity
NOK −618,000

Financial health · 2024

Liquidity
0.30
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-231.0%
Weak
Equity as a share of total capital

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

Who owns TOPP LEILIGHETER AS?

TOAM INVEST AS
TOPP LEILIGHETER AS
NOK 0 rev. · NOK −9,000 profit

TOPP LEILIGHETER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TOPP LEILIGHETER AS

Who owns TOPP LEILIGHETER AS?

TOAM INVEST AS is the largest registered owner, with 50.0%.

What is the revenue of TOPP LEILIGHETER AS?

TOPP LEILIGHETER AS had revenue of NOK 0 in 2024.

Who is the general manager of TOPP LEILIGHETER AS?

Petter Dahl is registered as general manager of TOPP LEILIGHETER AS.

Where is TOPP LEILIGHETER AS based?

TOPP LEILIGHETER AS has its business address in Oslo.

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.