BIZTRAC BETA
Rental and operating of own or leased real estate

NØSTHAUGEN EIENDOM AS

Org. no. 991257047 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 17.4m
Operating profit NOK 14.4m
Equity NOK 49.3m
Incorporated 2007
Share capital NOK 10.1m

Signals

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

NØSTHAUGEN EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 991257047. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 10.1m, divided into 1010000 shares. The company's stated purpose is: “Investering direkte og indirekte i fast eiendom, aksjer og andre eierandeler, samt all annen virksomhet som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 17.4m in revenue and NOK 14.4m in operating profit.

Key figures · 2024

Revenue
NOK 17.4m
Operating profit
NOK 14.4m
Equity
NOK 49.3m
Est. value
NOK 59.6m

Financial health · 2024

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

Who owns NØSTHAUGEN EIENDOM AS?

SPILLUM HANDELSPARK INVEST AS
NØSTHAUGEN EIENDOM AS
NOK 17.4m rev. · NOK 14.4m profit

NØSTHAUGEN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NØSTHAUGEN EIENDOM AS

Who owns NØSTHAUGEN EIENDOM AS?

SPILLUM HANDELSPARK INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of NØSTHAUGEN EIENDOM AS?

NØSTHAUGEN EIENDOM AS had revenue of NOK 17.4m in 2024.

Where is NØSTHAUGEN EIENDOM AS based?

NØSTHAUGEN EIENDOM 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.