BIZTRAC BETA
Temporary employment agency activities and other human resource provisions

DOVRE SOLUTIONS AS

Org. no. 912630714 Limited company (AS) Stavanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 691.2m
Operating profit NOK 18.3m
Equity NOK 76.6m
Incorporated 2013
Employees 249
Share capital NOK 2.6m

DOVRE SOLUTIONS AS is registered as a limited company in Stavanger, Rogaland with organisation number 912630714. The business is classified under temporary employment agency activities and other human resource provisions (NACE 78.200). The company was incorporated in 2013 and has 249 registered employees. Registered share capital is NOK 2.6m, divided into 25581403 shares. The company's stated purpose is: “Drive konsulenttjenester, kjøp og salg av verdipapirer samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 691.2m in revenue and NOK 18.3m in operating profit.

Key figures · 2024

Revenue
NOK 691.2m
Operating profit
NOK 18.3m
Equity
NOK 76.6m
Est. value
NOK 114.8m

Financial health · 2024

Liquidity
1.35
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.2%
Good
Equity as a share of total capital

Who owns DOVRE SOLUTIONS AS?

NYAB AB
DOVRE SOLUTIONS AS
NOK 691.2m rev. · NOK 18.3m profit

DOVRE SOLUTIONS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DOVRE SOLUTIONS AS

Who owns DOVRE SOLUTIONS AS?

NYAB AB is the largest registered owner, with 100.0%.

What is the revenue of DOVRE SOLUTIONS AS?

DOVRE SOLUTIONS AS had revenue of NOK 691.2m in 2024.

Who is the general manager of DOVRE SOLUTIONS AS?

Harald Vaagaasar Nikolaisen is registered as general manager of DOVRE SOLUTIONS AS.

Where is DOVRE SOLUTIONS AS based?

DOVRE SOLUTIONS AS has its business address in Stavanger.

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.