BIZTRAC BETA
Auditing

REVISJON 1 AS

Org. no. 988623512 Limited company (AS) Stavanger Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 2.8m
Equity NOK 2.3m
Incorporated 2005
Share capital NOK 100,000

REVISJON 1 AS is registered as a limited company in Stavanger, Rogaland with organisation number 988623512. The business is classified under auditing (NACE 69.201). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 2000 shares. The company's stated purpose is: “Revisjon, regnskapsføring og rådgivning og alt som hermed står i forbindelse, herunder å delta i andre selskap med lignende virksomhet. I tillegg skal selskapet kunne investere i andre aksjer samt eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 2.8m
Equity
NOK 2.3m
Est. value
NOK 10.3m

Financial health · 2024

Liquidity
1.62
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
52.6%
Very good
Equity as a share of total capital

Who owns REVISJON 1 AS?

ODD MARTHON FRØILAND
REVISJON 1 AS
NOK 5.6m rev. · NOK 2.8m profit

REVISJON 1 AS has 2 registered shareholders:

All shareholders and roles →

Which companies does REVISJON 1 AS own?

REVISJON 1 AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REVISJON 1 AS

Who owns REVISJON 1 AS?

ODD MARTHON FRØILAND is the largest registered owner, with 50.0%.

What is the revenue of REVISJON 1 AS?

REVISJON 1 AS had revenue of NOK 5.6m in 2024.

Who is the general manager of REVISJON 1 AS?

Odd Marthon Frøiland is registered as general manager of REVISJON 1 AS.

Where is REVISJON 1 AS based?

REVISJON 1 AS has its business address in Stavanger.

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.