BIZTRAC BETA
Rental and operating of own or leased real estate

ROA SENTERUTVIKLING AS

Org. no. 977270030 Limited company (AS) Bærum Incorporated 1996 Active
Ownership graph ↗
Revenue 2024 NOK 3.7m
Operating profit NOK 2.3m
Equity NOK 2.8m
Incorporated 1996
Share capital NOK 858,000

Signals

2 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-03-18 Adresseendring registrert 2026-03-18.

ROA SENTERUTVIKLING AS is registered as a limited company in Bærum, Akershus with organisation number 977270030. 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 858,000, divided into 8581 shares. The company's stated purpose is: “Erverv av tomtegrunn og utvikling av næringsareal, samt utleie av lokaler.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.7m in revenue and NOK 2.3m in operating profit.

Key figures · 2024

Revenue
NOK 3.7m
Operating profit
NOK 2.3m
Equity
NOK 2.8m
Est. value
NOK 4.9m

Financial health · 2024

Liquidity
2.46
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

Who owns ROA SENTERUTVIKLING AS?

WOLFF EIENDOM AS
ROA SENTERUTVIKLING AS
NOK 3.7m rev. · NOK 2.3m profit

ROA SENTERUTVIKLING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROA SENTERUTVIKLING AS

Who owns ROA SENTERUTVIKLING AS?

WOLFF EIENDOM AS is the largest registered owner, with 100.0%.

What is the revenue of ROA SENTERUTVIKLING AS?

ROA SENTERUTVIKLING AS had revenue of NOK 3.7m in 2024.

Where is ROA SENTERUTVIKLING AS based?

ROA SENTERUTVIKLING AS has its business address in Lysaker.

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.