BIZTRAC BETA
Accounting and bookkeeping

KOMPLETT REGNSKAP AS

Org. no. 933565831 Limited company (AS) Haugesund Incorporated 1983 Active
Ownership graph ↗
Revenue 2025 NOK 11.9m
Operating profit NOK 2.7m
Equity NOK 1.1m
Incorporated 1983
Employees 9
Share capital NOK 100,000

KOMPLETT REGNSKAP AS is registered as a limited company in Haugesund, Rogaland with organisation number 933565831. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 1983 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Regnskaps- kontor-/administrasjonsoppdrag, salg og servicetjenester samt hva dermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.9m in revenue and NOK 2.7m in operating profit.

Key figures · 2025

Revenue
NOK 11.9m
Operating profit
NOK 2.7m
Equity
NOK 1.1m
Est. value
NOK 11.0m

Financial health · 2025

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

Who owns KOMPLETT REGNSKAP AS?

EVELYN SØRENES AS
KOMPLETT REGNSKAP AS
NOK 11.9m rev. · NOK 2.7m profit

KOMPLETT REGNSKAP AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about KOMPLETT REGNSKAP AS

Who owns KOMPLETT REGNSKAP AS?

EVELYN SØRENES AS is the largest registered owner, with 45.0%.

What is the revenue of KOMPLETT REGNSKAP AS?

KOMPLETT REGNSKAP AS had revenue of NOK 11.9m in 2025.

Who is the general manager of KOMPLETT REGNSKAP AS?

Annette Ravdal is registered as general manager of KOMPLETT REGNSKAP AS.

Where is KOMPLETT REGNSKAP AS based?

KOMPLETT REGNSKAP AS has its business address in Haugesund.

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.