BIZTRAC BETA
Auditing

STORMO REVISJON AS

Org. no. 831797622 Limited company (AS) Kristiansund Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.0m
Operating profit NOK 632,000
Equity NOK 31,000
Incorporated 2023
Share capital NOK 30,000

STORMO REVISJON AS is registered as a limited company in Kristiansund, Møre og Romsdal with organisation number 831797622. The business is classified under auditing (NACE 69.201). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Revisjon, konsulentvirksomhet, regnskap- og forretningsførsel for andre, utleie av arbeidskraft og tjenester og hva hermed står i forbindelse med dette, herunder å delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.0m in revenue and NOK 632,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.0m
Operating profit
NOK 632,000
Equity
NOK 31,000
Est. value
NOK 2.6m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns STORMO REVISJON AS?

STORMO HOLDING AS
STORMO REVISJON AS
NOK 3.0m rev. · NOK 632,000 profit

STORMO REVISJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STORMO REVISJON AS

Who owns STORMO REVISJON AS?

STORMO HOLDING AS is the largest registered owner, with 99.0%.

What is the revenue of STORMO REVISJON AS?

STORMO REVISJON AS had revenue of NOK 3.0m in 2025.

Who is the general manager of STORMO REVISJON AS?

Roger Stormo is registered as general manager of STORMO REVISJON AS.

Where is STORMO REVISJON AS based?

STORMO REVISJON AS has its business address in Kristiansund N.

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.