biztrac. BETA
COMPANY REGISTER PROFILE
996806030 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Activities of housing cooperatives

GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE

Org. no. 996806030 Condominium flat owner (ESEK) Oslo Incorporated 2008 Active
Revenue 2025 NOK 2.5m
Operating profit NOK −1.6m
Equity NOK 65,000
Incorporated 2008

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−1,6 mill kr).

GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE is registered as a condominium flat owner in Oslo, Oslo with organisation number 996806030. The business is classified under activities of housing cooperatives (NACE 97.001). The company was incorporated in 2008. The company's stated purpose is: “Eierseksjonssameie”. The most recent filed accounts, for the 2025 financial year, show NOK 2.5m in revenue and NOK −1.6m in operating profit.

Former names: GAUSTADTOPPEN LODGE EIERSEKSJONSSAMEIE

Key figures · 2025

Revenue
NOK 2.5m
▲ +61 %
Operating profit
NOK −1.6m
▼ −878 %
Equity
NOK 65,000
▼ −96 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
1.47
Satisfactory
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
31.8%
Weak
Equity as a share of total capital

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

Who owns GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE?

No shareholders are registered for GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE

What is the revenue of GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE?

GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE had revenue of NOK 2.5m in 2025.

Where is GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE based?

GAUSTATOPPEN LODGE EIERSEKSJONSSAMEIE has its business address in Oslo.

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

Report a problem

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