BIZTRAC BETA
Auditing

TRØNDELAG REVISJON AS

Org. no. 995683555 Limited company (AS) Levanger Incorporated 2010 Active
Ownership graph ↗
Revenue 2024 NOK 8.8m
Operating profit NOK 481,000
Equity NOK 930,000
Incorporated 2010
Employees 6
Share capital NOK 100,000

TRØNDELAG REVISJON AS is registered as a limited company in Levanger, Trøndelag with organisation number 995683555. The business is classified under auditing (NACE 69.201). The company was incorporated in 2010 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Revisjon og økonomisk rådgivning, samt annen virksomhet som står i naturlig forbindelse med dette, herunder å delta i andre selskap med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.8m in revenue and NOK 481,000 in operating profit.

Key figures · 2024

Revenue
NOK 8.8m
Operating profit
NOK 481,000
Equity
NOK 930,000
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns TRØNDELAG REVISJON AS?

A. VANG HOLDING AS
TRØNDELAG REVISJON AS
NOK 8.8m rev. · NOK 481,000 profit

TRØNDELAG REVISJON AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about TRØNDELAG REVISJON AS

Who owns TRØNDELAG REVISJON AS?

A. VANG HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of TRØNDELAG REVISJON AS?

TRØNDELAG REVISJON AS had revenue of NOK 8.8m in 2024.

Who is the general manager of TRØNDELAG REVISJON AS?

Asle Vang is registered as general manager of TRØNDELAG REVISJON AS.

Where is TRØNDELAG REVISJON AS based?

TRØNDELAG REVISJON AS has its business address in Levanger.

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.