BIZTRAC BETA
Rental and operating of own or leased real estate

NR5 EIENDOM AS

Org. no. 993345881 Limited company (AS) Bærum Incorporated 2008 Active
Ownership graph ↗
Revenue 2025 NOK 6.2m
Operating profit NOK 335,000
Equity NOK 21.4m
Incorporated 2008
Share capital NOK 2.0m

Signals

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

NR5 EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 993345881. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 2.0m, divided into 100 shares. The company's stated purpose is: “Handel med, investering i og utleie av fast eiendom, samt handel med og investering i verdipapirer og andre formuesobjekter, herunder deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.2m in revenue and NOK 335,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.2m
Operating profit
NOK 335,000
Equity
NOK 21.4m
Est. value
NOK 15.3m

Financial health · 2025

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

Who owns NR5 EIENDOM AS?

BWF AS
NR5 EIENDOM AS
NOK 6.2m rev. · NOK 335,000 profit

NR5 EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Group structure

NR5 EIENDOM AS er morselskap for 5 datterselskaper:

Frequently asked questions about NR5 EIENDOM AS

Who owns NR5 EIENDOM AS?

BWF AS is the largest registered owner, with 100.0%.

What is the revenue of NR5 EIENDOM AS?

NR5 EIENDOM AS had revenue of NOK 6.2m in 2025.

Where is NR5 EIENDOM AS based?

NR5 EIENDOM AS has its business address in Rud.

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.