BIZTRAC BETA
Rental and operating of own or leased real estate

ROSENLUND KONTORBYGG AS

Org. no. 815956192 Limited company (AS) Oslo Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 50.1m
Operating profit NOK 24.0m
Equity NOK 420.5m
Incorporated 2015
Share capital NOK 30,000

Signals

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

ROSENLUND KONTORBYGG AS is registered as a limited company in Oslo, Oslo with organisation number 815956192. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 30 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 50.1m in revenue and NOK 24.0m in operating profit.

Key figures · 2024

Revenue
NOK 50.1m
Operating profit
NOK 24.0m
Equity
NOK 420.5m
Est. value
NOK 357.8m

Financial health · 2024

Liquidity
0.14
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
92.7%
Very good
Equity as a share of total capital

Who owns ROSENLUND KONTORBYGG AS?

NJORD PROSJEKT 45 AS
ROSENLUND KONTORBYGG AS
NOK 50.1m rev. · NOK 24.0m profit

ROSENLUND KONTORBYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROSENLUND KONTORBYGG AS

Who owns ROSENLUND KONTORBYGG AS?

NJORD PROSJEKT 45 AS is the largest registered owner, with 100.0%.

What is the revenue of ROSENLUND KONTORBYGG AS?

ROSENLUND KONTORBYGG AS had revenue of NOK 50.1m in 2024.

Where is ROSENLUND KONTORBYGG AS based?

ROSENLUND KONTORBYGG 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.