BIZTRAC BETA
Auditing

REVISJONSFIRMA TORBJØRN SALVESEN AS

Org. no. 988958638 Limited company (AS) Kristiansand Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 1.9m
Equity NOK 475,000
Incorporated 2005
Share capital NOK 100,000

REVISJONSFIRMA TORBJØRN SALVESEN AS is registered as a limited company in Kristiansand, Agder with organisation number 988958638. The business is classified under auditing (NACE 69.201). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drive revisjon, regnskapsføring og økonomisk rådgivning.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 1.9m in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 1.9m
Equity
NOK 475,000
Est. value
NOK 6.2m

Financial health · 2025

Liquidity
1.23
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
18.5%
Good
Equity as a share of total capital

Who owns REVISJONSFIRMA TORBJØRN SALVESEN AS?

TORBJØRN SALVESEN
REVISJONSFIRMA TORBJØRN SALVESEN AS
NOK 3.5m rev. · NOK 1.9m profit

REVISJONSFIRMA TORBJØRN SALVESEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REVISJONSFIRMA TORBJØRN SALVESEN AS

Who owns REVISJONSFIRMA TORBJØRN SALVESEN AS?

TORBJØRN SALVESEN is the largest registered owner, with 100.0%.

What is the revenue of REVISJONSFIRMA TORBJØRN SALVESEN AS?

REVISJONSFIRMA TORBJØRN SALVESEN AS had revenue of NOK 3.5m in 2025.

Who is the general manager of REVISJONSFIRMA TORBJØRN SALVESEN AS?

Torbjørn Salvesen is registered as general manager of REVISJONSFIRMA TORBJØRN SALVESEN AS.

Where is REVISJONSFIRMA TORBJØRN SALVESEN AS based?

REVISJONSFIRMA TORBJØRN SALVESEN AS has its business address in Kristiansand S.

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.