biztrac. BETA
COMPANY REGISTER PROFILE
983437524 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

ROLFSBUKTA AS

Org. no. 983437524 Limited company (AS) Bærum Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 948,000
Operating profit NOK 788,000
Equity NOK 16.3m
Incorporated 2001
Share capital NOK 3.6m

ROLFSBUKTA AS is registered as a limited company in Bærum, Akershus with organisation number 983437524. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2001. Registered share capital is NOK 3.6m, divided into 3633446 shares. The company's stated purpose is: “Erverve, utvikle og selge fast eiendom, samt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 948,000 in revenue and NOK 788,000 in operating profit.

Key figures · 2025

Revenue
NOK 948,000
▲ +392 %
Operating profit
NOK 788,000
▲ +255 %
Equity
NOK 16.3m
▼ −48 %
Est. value
NOK 13.8m

Financial health · 2025

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
57.2%
Very good
Equity as a share of total capital

Who owns ROLFSBUKTA AS?

ROLFSBUKTA AS
NOK 948,000 rev. · NOK 788,000 profit

ROLFSBUKTA AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ROLFSBUKTA AS own?

ROLFSBUKTA AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ROLFSBUKTA AS er morselskap for 67 datterselskaper:

Frequently asked questions about ROLFSBUKTA AS

Who owns ROLFSBUKTA AS?

OBOS FORNEBU AS is the largest registered owner, with 100.0%.

What is the revenue of ROLFSBUKTA AS?

ROLFSBUKTA AS had revenue of NOK 948,000 in 2025.

Where is ROLFSBUKTA AS based?

ROLFSBUKTA AS has its business address in Fornebu.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.