BIZTRAC BETA
Auditing

REVISOR KLOKK AS

Org. no. 999125484 Limited company (AS) Sykkylven Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 5.7m
Operating profit NOK 1.0m
Equity NOK 529,000
Incorporated 2012
Employees 5
Share capital NOK 100,000

REVISOR KLOKK AS is registered as a limited company in Sykkylven, Møre og Romsdal with organisation number 999125484. The business is classified under auditing (NACE 69.201). The company was incorporated in 2012 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Revisjon, regnskapsføring for andre, konsulentvirksomhet og rådgivning, direkte eller gjennom deltagelse i andre selskaper og virksomheter, og det som hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.7m in revenue and NOK 1.0m in operating profit.

Key figures · 2024

Revenue
NOK 5.7m
Operating profit
NOK 1.0m
Equity
NOK 529,000
Est. value
NOK 4.9m

Financial health · 2024

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

Who owns REVISOR KLOKK AS?

AUSKJERET AS
REVISOR KLOKK AS
NOK 5.7m rev. · NOK 1.0m profit

REVISOR KLOKK AS has 3 registered shareholders:

All shareholders and roles →

Group structure

REVISOR KLOKK AS er morselskap for 2 datterselskaper:

Frequently asked questions about REVISOR KLOKK AS

Who owns REVISOR KLOKK AS?

AUSKJERET AS is the largest registered owner, with 99.5%.

What is the revenue of REVISOR KLOKK AS?

REVISOR KLOKK AS had revenue of NOK 5.7m in 2024.

Who is the general manager of REVISOR KLOKK AS?

Tormod Klokk is registered as general manager of REVISOR KLOKK AS.

Where is REVISOR KLOKK AS based?

REVISOR KLOKK AS has its business address in Sykkylven.

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.