BIZTRAC BETA
Auditing

VALENTOR REVISJON AS

Org. no. 997088980 Limited company (AS) Lillehammer Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 1.3m
Equity NOK 2.6m
Incorporated 2011
Employees 6
Share capital NOK 100,000

VALENTOR REVISJON AS is registered as a limited company in Lillehammer, Innlandet with organisation number 997088980. The business is classified under auditing (NACE 69.201). The company was incorporated in 2011 and has 6 registered employees. Registered share capital is NOK 100,000, divided into 1003 shares. The company's stated purpose is: “Revisjon og bistand knyttet til det. Regnskapstjenester. Selskapet kan også ved aksjetegning eller på annen måte gjøre seg interessert i andre foretagende, samt kjøpe, eie og selge fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 1.3m in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 1.3m
Equity
NOK 2.6m
Est. value
NOK 7.9m

Financial health · 2024

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

Who owns VALENTOR REVISJON AS?

DOVRE REVISJON AS
VALENTOR REVISJON AS
NOK 9.5m rev. · NOK 1.3m profit

VALENTOR REVISJON AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about VALENTOR REVISJON AS

Who owns VALENTOR REVISJON AS?

DOVRE REVISJON AS is the largest registered owner, with 33.3%.

What is the revenue of VALENTOR REVISJON AS?

VALENTOR REVISJON AS had revenue of NOK 9.5m in 2024.

Who is the general manager of VALENTOR REVISJON AS?

Roar Rudiløkken is registered as general manager of VALENTOR REVISJON AS.

Where is VALENTOR REVISJON AS based?

VALENTOR REVISJON AS has its business address in Lillehammer.

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.