BIZTRAC BETA
Auditing

REVISORHUSET INVEST AS

Org. no. 989675893 Limited company (AS) Ringerike Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 546,000
Equity NOK 7.3m
Incorporated 2006
Share capital NOK 1.0m

Signals

1 flags
  • Nylig endring 2026-06-17 Avregistrert registrert 2026-06-17.

REVISORHUSET INVEST AS is registered as a limited company in Ringerike, Buskerud with organisation number 989675893. The business is classified under auditing (NACE 69.201). The company was incorporated in 2006. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Revisjonsvirksomhet samt å ha eierandeler i andre revisjonsselskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 546,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 546,000
Equity
NOK 7.3m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns REVISORHUSET INVEST AS?

HVERVEN INVEST AS
REVISORHUSET INVEST AS
NOK 1.8m rev. · NOK 546,000 profit

REVISORHUSET INVEST AS has 7 registered shareholders:

All shareholders and roles →

Which companies does REVISORHUSET INVEST AS own?

REVISORHUSET INVEST AS holds a stake in 1 company:

See the full ownership structure →

Group structure

REVISORHUSET INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about REVISORHUSET INVEST AS

Who owns REVISORHUSET INVEST AS?

HVERVEN INVEST AS is the largest registered owner, with 55.0%.

What is the revenue of REVISORHUSET INVEST AS?

REVISORHUSET INVEST AS had revenue of NOK 1.8m in 2025.

Where is REVISORHUSET INVEST AS based?

REVISORHUSET INVEST AS has its business address in Hønefoss.

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.