BIZTRAC BETA
Auditing

REVISORHUSET AS

Org. no. 987610859 Limited company (AS) Oslo Incorporated 2004 Active
Ownership graph ↗
Revenue 2024 NOK 32.3m
Operating profit NOK 3.1m
Equity NOK 4.9m
Incorporated 2004
Employees 11
Share capital NOK 2.6m

REVISORHUSET AS is registered as a limited company in Oslo, Oslo with organisation number 987610859. The business is classified under auditing (NACE 69.201). The company was incorporated in 2004 and has 11 registered employees. Registered share capital is NOK 2.6m, divided into 26180 shares. The company's stated purpose is: “Revisjon- og konsulentvirksomhet, samt å delta i andre selskaper med beslektet virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 32.3m in revenue and NOK 3.1m in operating profit.

Key figures · 2024

Revenue
NOK 32.3m
Operating profit
NOK 3.1m
Equity
NOK 4.9m
Est. value
NOK 17.4m

Financial health · 2024

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

Who owns REVISORHUSET AS?

CK HOLDING AS
REVISORHUSET AS
NOK 32.3m rev. · NOK 3.1m profit

REVISORHUSET AS has 5 registered shareholders:

All shareholders and roles →

Which companies does REVISORHUSET AS own?

REVISORHUSET AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

REVISORHUSET AS er morselskap for 2 datterselskaper:

Frequently asked questions about REVISORHUSET AS

Who owns REVISORHUSET AS?

CK HOLDING AS is the largest registered owner, with 99.7%.

What is the revenue of REVISORHUSET AS?

REVISORHUSET AS had revenue of NOK 32.3m in 2024.

Who is the general manager of REVISORHUSET AS?

Kai Magnar Killingmo is registered as general manager of REVISORHUSET AS.

Where is REVISORHUSET AS based?

REVISORHUSET 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.