BIZTRAC BETA
Rental and operating of own or leased real estate

NADDERUD EIENDOM AS

Org. no. 977050049 Limited company (AS) Oslo Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 1.3m
Operating profit NOK 517,000
Equity NOK 1.7m
Incorporated 1996
Share capital NOK 800,000

Signals

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

NADDERUD EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 977050049. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 800,000. The company's stated purpose is: “Kjøp og utvikling av eiendommer, utbygging av tomter, kjøp og drift av næringseiendommer, deltagelse i tilsvarende prosjekter og annen virksomhet som er naturlig furbundet med det foran nevnte.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.3m in revenue and NOK 517,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.3m
Operating profit
NOK 517,000
Equity
NOK 1.7m
Est. value
NOK 2.1m

Financial health · 2025

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

Who owns NADDERUD EIENDOM AS?

REBUS STOR-OSLO AS
NADDERUD EIENDOM AS
NOK 1.3m rev. · NOK 517,000 profit

NADDERUD EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NADDERUD EIENDOM AS

Who owns NADDERUD EIENDOM AS?

REBUS STOR-OSLO AS is the largest registered owner, with 100.0%.

What is the revenue of NADDERUD EIENDOM AS?

NADDERUD EIENDOM AS had revenue of NOK 1.3m in 2025.

Where is NADDERUD EIENDOM AS based?

NADDERUD 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.