BIZTRAC BETA
Plumbing installation

VENTILASJON & BRANNTEKNIKK AS

Org. no. 917545685 Limited company (AS) Bamble Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 46,000
Operating profit NOK 2,000
Equity NOK 12,000
Incorporated 2016
Share capital NOK 30,000

VENTILASJON & BRANNTEKNIKK AS is registered as a limited company in Bamble, Telemark with organisation number 917545685. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Ventilasjons og brannteknisk arbeid.”. The most recent filed accounts, for the 2024 financial year, show NOK 46,000 in revenue and NOK 2,000 in operating profit.

Key figures · 2024

Revenue
NOK 46,000
Operating profit
NOK 2,000
Equity
NOK 12,000
Est. value
NOK 14,000

Financial health · 2024

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns VENTILASJON & BRANNTEKNIKK AS?

JONNY HOLM OLSEN
VENTILASJON & BRANNTEKNIKK AS
NOK 46,000 rev. · NOK 2,000 profit

VENTILASJON & BRANNTEKNIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VENTILASJON & BRANNTEKNIKK AS

Who owns VENTILASJON & BRANNTEKNIKK AS?

JONNY HOLM OLSEN is the largest registered owner, with 100.0%.

What is the revenue of VENTILASJON & BRANNTEKNIKK AS?

VENTILASJON & BRANNTEKNIKK AS had revenue of NOK 46,000 in 2024.

Who is the general manager of VENTILASJON & BRANNTEKNIKK AS?

Jonny Holm Olsen is registered as general manager of VENTILASJON & BRANNTEKNIKK AS.

Where is VENTILASJON & BRANNTEKNIKK AS based?

VENTILASJON & BRANNTEKNIKK AS has its business address in Stathelle.

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.