BIZTRAC BETA
Auditing

LERVIK REVISJON AS

Org. no. 970902279 Limited company (AS) Fredrikstad Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 2.3m
Operating profit NOK 865,000
Equity NOK 833,000
Incorporated 1994
Share capital NOK 100,000

LERVIK REVISJON AS is registered as a limited company in Fredrikstad, Østfold with organisation number 970902279. The business is classified under auditing (NACE 69.201). The company was incorporated in 1994. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Selskapets formål er yting av revisjonstjenester og annen tjenesteyting i forbindelse med dette, ekstern regnskapsføring, kjøp og salg av aksjer, kjøp, salg og drift av fast eiendom samt leie, utleie og handel. Herunder også deltakelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.3m in revenue and NOK 865,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.3m
Operating profit
NOK 865,000
Equity
NOK 833,000
Est. value
NOK 3.2m

Financial health · 2024

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

Who owns LERVIK REVISJON AS?

BOOKMAN AS
LERVIK REVISJON AS
NOK 2.3m rev. · NOK 865,000 profit

LERVIK REVISJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LERVIK REVISJON AS

Who owns LERVIK REVISJON AS?

BOOKMAN AS is the largest registered owner, with 99.9%.

What is the revenue of LERVIK REVISJON AS?

LERVIK REVISJON AS had revenue of NOK 2.3m in 2024.

Who is the general manager of LERVIK REVISJON AS?

Jan Trygve Lervik is registered as general manager of LERVIK REVISJON AS.

Where is LERVIK REVISJON AS based?

LERVIK REVISJON AS has its business address in Kråkerøy.

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.