BIZTRAC BETA
Other construction installation

V8 VENTILASJON AS

Org. no. 914243343 Limited company (AS) Lillestrøm Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 9.5m
Operating profit NOK 1.2m
Equity NOK 1.7m
Incorporated 2014
Employees 7
Share capital NOK 30,000

V8 VENTILASJON AS is registered as a limited company in Lillestrøm, Akershus with organisation number 914243343. The business is classified under other construction installation (NACE 43.240). The company was incorporated in 2014 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Plåt og ventilasjonsmontasje/service og mekanisk virksomhet, samt handel med varer innenfor dette området og alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.5m in revenue and NOK 1.2m in operating profit.

Key figures · 2024

Revenue
NOK 9.5m
Operating profit
NOK 1.2m
Equity
NOK 1.7m
Est. value
NOK 4.2m

Financial health · 2024

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

Who owns V8 VENTILASJON AS?

FREDRIK ALEXANDER AXELSSON
V8 VENTILASJON AS
NOK 9.5m rev. · NOK 1.2m profit

V8 VENTILASJON AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about V8 VENTILASJON AS

Who owns V8 VENTILASJON AS?

FREDRIK ALEXANDER AXELSSON is the largest registered owner, with 100.0%.

What is the revenue of V8 VENTILASJON AS?

V8 VENTILASJON AS had revenue of NOK 9.5m in 2024.

Who is the general manager of V8 VENTILASJON AS?

Fredrik Alexander Axelsson is registered as general manager of V8 VENTILASJON AS.

Where is V8 VENTILASJON AS based?

V8 VENTILASJON AS has its business address in Lillestrøm.

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.