BIZTRAC BETA
Auditing

TORVUND REVISJON AS

Org. no. 993550914 Limited company (AS) Bergen Incorporated 2009 Active
Ownership graph ↗
Revenue 2025 NOK 4.5m
Operating profit NOK 1.8m
Equity NOK 4.0m
Incorporated 2009
Share capital NOK 30,000

TORVUND REVISJON AS is registered as a limited company in Bergen, Vestland with organisation number 993550914. The business is classified under auditing (NACE 69.201). The company was incorporated in 2009. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Revisjon, konsulentvirksomhet og regnskapsføring og alt hva der står i forbindelse, herunder også delta i andre selskaper med liknende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.5m in revenue and NOK 1.8m in operating profit.

Key figures · 2025

Revenue
NOK 4.5m
Operating profit
NOK 1.8m
Equity
NOK 4.0m
Est. value
NOK 8.5m

Financial health · 2025

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

Who owns TORVUND REVISJON AS?

KRISTIAN TORVUND
TORVUND REVISJON AS
NOK 4.5m rev. · NOK 1.8m profit

TORVUND REVISJON AS has 1 registered shareholder:

All shareholders and roles →

Which companies does TORVUND REVISJON AS own?

TORVUND REVISJON AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about TORVUND REVISJON AS

Who owns TORVUND REVISJON AS?

KRISTIAN TORVUND is the largest registered owner, with 100.0%.

What is the revenue of TORVUND REVISJON AS?

TORVUND REVISJON AS had revenue of NOK 4.5m in 2025.

Who is the general manager of TORVUND REVISJON AS?

Kristian Torvund is registered as general manager of TORVUND REVISJON AS.

Where is TORVUND REVISJON AS based?

TORVUND REVISJON AS has its business address in Bergen.

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.