BIZTRAC BETA
Rental and operating of own or leased real estate

NØTTERØY NÆRINGSEIENDOM AS

Org. no. 910405292 Limited company (AS) Oslo Incorporated 1970 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 1.9m
Equity NOK 589,000
Incorporated 1970
Share capital NOK 95,000

Signals

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

NØTTERØY NÆRINGSEIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 910405292. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1970. Registered share capital is NOK 95,000, divided into 100000 shares. The company's stated purpose is: “Investere i fast eiendom eller selskaper som eier fast eiendom, og alt som dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 1.9m in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 1.9m
Equity
NOK 589,000
Est. value
NOK 4.0m

Financial health · 2024

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

Who owns NØTTERØY NÆRINGSEIENDOM AS?

LØVENSKIOLD-VÆKERØ AS
NØTTERØY NÆRINGSEIENDOM AS
NOK 2.0m rev. · NOK 1.9m profit

NØTTERØY NÆRINGSEIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NØTTERØY NÆRINGSEIENDOM AS

Who owns NØTTERØY NÆRINGSEIENDOM AS?

LØVENSKIOLD-VÆKERØ AS is the largest registered owner, with 100.0%.

What is the revenue of NØTTERØY NÆRINGSEIENDOM AS?

NØTTERØY NÆRINGSEIENDOM AS had revenue of NOK 2.0m in 2024.

Where is NØTTERØY NÆRINGSEIENDOM AS based?

NØTTERØY NÆRINGSEIENDOM 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.