BIZTRAC BETA
Auditing

RE REVISJON AS

Org. no. 818091702 Limited company (AS) Tønsberg Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 15.0m
Operating profit NOK 3.8m
Equity NOK 3.2m
Incorporated 2016
Employees 12
Share capital NOK 100,000

RE REVISJON AS is registered as a limited company in Tønsberg, Vestfold with organisation number 818091702. The business is classified under auditing (NACE 69.201). The company was incorporated in 2016 and has 12 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Utføre revisjon, regnskapsføring og rådgivning, herunder deltakelse i andre selskaper og hva som derved står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.0m in revenue and NOK 3.8m in operating profit.

Key figures · 2025

Revenue
NOK 15.0m
Operating profit
NOK 3.8m
Equity
NOK 3.2m
Est. value
NOK 15.5m

Financial health · 2025

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

Who owns RE REVISJON AS?

WIKTORIN RÅDGIVNING OG INVEST AS
RE REVISJON AS
NOK 15.0m rev. · NOK 3.8m profit

RE REVISJON AS has 4 registered shareholders:

All shareholders and roles →

Which companies does RE REVISJON AS own?

RE REVISJON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RE REVISJON AS

Who owns RE REVISJON AS?

WIKTORIN RÅDGIVNING OG INVEST AS is the largest registered owner, with 54.0%.

What is the revenue of RE REVISJON AS?

RE REVISJON AS had revenue of NOK 15.0m in 2025.

Who is the general manager of RE REVISJON AS?

Christian Lærum Wiktorin is registered as general manager of RE REVISJON AS.

Where is RE REVISJON AS based?

RE REVISJON AS has its business address in Revetal.

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.