BIZTRAC BETA
Auditing

SYSTEMREVISJON AS

Org. no. 821154022 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 7.4m
Operating profit NOK 4.6m
Equity NOK 261,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SYSTEMREVISJON AS is registered as a limited company in Oslo, Oslo with organisation number 821154022. The business is classified under auditing (NACE 69.201). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Revisjon, regnskapsføring, bedriftsrådgivning og tjenester som naturlig er beslektet, samt deltagelse i andre virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.4m in revenue and NOK 4.6m in operating profit.

Key figures · 2024

Revenue
NOK 7.4m
Operating profit
NOK 4.6m
Equity
NOK 261,000
Est. value
NOK 14.0m

Financial health · 2024

Liquidity
1.04
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
4.2%
Weak
Equity as a share of total capital

Who owns SYSTEMREVISJON AS?

REVISJONSFIRMAET FLATTUM & CO AS
SYSTEMREVISJON AS
NOK 7.4m rev. · NOK 4.6m profit

SYSTEMREVISJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYSTEMREVISJON AS

Who owns SYSTEMREVISJON AS?

REVISJONSFIRMAET FLATTUM & CO AS is the largest registered owner, with 100.0%.

What is the revenue of SYSTEMREVISJON AS?

SYSTEMREVISJON AS had revenue of NOK 7.4m in 2024.

Who is the general manager of SYSTEMREVISJON AS?

Thorbjørn Grindhaug is registered as general manager of SYSTEMREVISJON AS.

Where is SYSTEMREVISJON AS based?

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