BIZTRAC BETA
Construction of residential and non-residential buildings

ROSER BOLIG AS

Org. no. 921142358 Limited company (AS) Tønsberg Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 16.0m
Operating profit NOK −15,000
Equity NOK 2.0m
Incorporated 2018
Employees 5
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).

ROSER BOLIG AS is registered as a limited company in Tønsberg, Vestfold with organisation number 921142358. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2018 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Renovering og bygging av boliger samt investering i eiendom og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 16.0m in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 16.0m
Operating profit
NOK −15,000
Equity
NOK 2.0m
Est. value
NOK 5.6m

Financial health · 2024

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

Who owns ROSER BOLIG AS?

MORTEN ROSER
ROSER BOLIG AS
NOK 16.0m rev. · NOK −15,000 profit

ROSER BOLIG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROSER BOLIG AS

Who owns ROSER BOLIG AS?

MORTEN ROSER is the largest registered owner, with 100.0%.

What is the revenue of ROSER BOLIG AS?

ROSER BOLIG AS had revenue of NOK 16.0m in 2024.

Who is the general manager of ROSER BOLIG AS?

Morten Roser is registered as general manager of ROSER BOLIG AS.

Where is ROSER BOLIG AS based?

ROSER BOLIG AS has its business address in Tønsberg.

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.