BIZTRAC BETA
Construction of residential and non-residential buildings

ROLFSEN EIENDOMSERVICE AS

Org. no. 922156638 Limited company (AS) Larvik Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 561,000
Equity NOK 1.6m
Incorporated 2019
Share capital NOK 30,000

ROLFSEN EIENDOMSERVICE AS is registered as a limited company in Larvik, Vestfold with organisation number 922156638. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tømrerarbeid, vedlikeholdsarbeid, vaktmestertjenester o.l. for bygg og eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 561,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 561,000
Equity
NOK 1.6m
Est. value
NOK 2.6m

Financial health · 2025

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

Who owns ROLFSEN EIENDOMSERVICE AS?

HANS MARIUS ROLFSEN
ROLFSEN EIENDOMSERVICE AS
NOK 3.0m rev. · NOK 561,000 profit

ROLFSEN EIENDOMSERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ROLFSEN EIENDOMSERVICE AS

Who owns ROLFSEN EIENDOMSERVICE AS?

HANS MARIUS ROLFSEN is the largest registered owner, with 100.0%.

What is the revenue of ROLFSEN EIENDOMSERVICE AS?

ROLFSEN EIENDOMSERVICE AS had revenue of NOK 3.0m in 2025.

Who is the general manager of ROLFSEN EIENDOMSERVICE AS?

Hans Marius Rolfsen is registered as general manager of ROLFSEN EIENDOMSERVICE AS.

Where is ROLFSEN EIENDOMSERVICE AS based?

ROLFSEN EIENDOMSERVICE AS has its business address in Larvik.

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.