BIZTRAC BETA
Ventilation installation

VENTIRENS AS

Org. no. 998790735 Limited company (AS) Frogn Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −52,000
Equity NOK −218,000
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−218k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−52k kr).

VENTIRENS AS is registered as a limited company in Frogn, Akershus with organisation number 998790735. The business is classified under ventilation installation (NACE 43.223). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Selskapets virksomhet er rensing/montering og service av ventilasjonsanlegg, og det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −52,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −52,000
Equity
NOK −218,000

Financial health · 2025

Liquidity
0.18
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-196.5%
Weak
Equity as a share of total capital

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

Who owns VENTIRENS AS?

TERJE HJERPSETH
VENTIRENS AS
NOK 1.1m rev. · NOK −52,000 profit

VENTIRENS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VENTIRENS AS

Who owns VENTIRENS AS?

TERJE HJERPSETH is the largest registered owner, with 51.0%.

What is the revenue of VENTIRENS AS?

VENTIRENS AS had revenue of NOK 1.1m in 2025.

Who is the general manager of VENTIRENS AS?

Terje Hjerpseth is registered as general manager of VENTIRENS AS.

Where is VENTIRENS AS based?

VENTIRENS AS has its business address in Drøbak.

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.