BIZTRAC BETA
Plumbing installation

HELGEMO VVS AS

Org. no. 929145437 Limited company (AS) Trondheim Incorporated 1980 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −120,000
Equity NOK 7.9m
Incorporated 1980
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−120k kr).

HELGEMO VVS AS is registered as a limited company in Trondheim, Trøndelag with organisation number 929145437. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 1980. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Rørleggervirksomhet, samt ved aksjetegning eller på annen måte delta i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −120,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −120,000
Equity
NOK 7.9m
Est. value
NOK 8.1m

Financial health · 2024

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

Who owns HELGEMO VVS AS?

KJELL INGAR HELGEMO
HELGEMO VVS AS
NOK 0 rev. · NOK −120,000 profit

HELGEMO VVS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HELGEMO VVS AS own?

HELGEMO VVS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HELGEMO VVS AS

Who owns HELGEMO VVS AS?

KJELL INGAR HELGEMO is the largest registered owner, with 100.0%.

What is the revenue of HELGEMO VVS AS?

HELGEMO VVS AS had revenue of NOK 0 in 2024.

Who is the general manager of HELGEMO VVS AS?

Kjell Ingar Helgemo is registered as general manager of HELGEMO VVS AS.

Where is HELGEMO VVS AS based?

HELGEMO VVS AS has its business address in Tiller.

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.