BIZTRAC BETA
Plumbing installation

HJELMÅS VVS AS

Org. no. 988410586 Limited company (AS) Alver Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 31.0m
Operating profit NOK 810,000
Equity NOK 7.0m
Incorporated 2005
Employees 32
Share capital NOK 177,000

HJELMÅS VVS AS is registered as a limited company in Alver, Vestland with organisation number 988410586. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2005 and has 32 registered employees. Registered share capital is NOK 177,000, divided into 500 shares. The company's stated purpose is: “Rørleggervirksomhet og hva som står i naturlig forbindelse med dette, herunder kjøp og salg av VVS produkter, og kjøp og salg av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 31.0m in revenue and NOK 810,000 in operating profit.

Key figures · 2024

Revenue
NOK 31.0m
Operating profit
NOK 810,000
Equity
NOK 7.0m
Est. value
NOK 5.1m

Financial health · 2024

Liquidity
1.50
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
31.1%
Good
Equity as a share of total capital

Who owns HJELMÅS VVS AS?

FÅVNE HOLDING AS
HJELMÅS VVS AS
NOK 31.0m rev. · NOK 810,000 profit

HJELMÅS VVS AS has 5 registered shareholders:

All shareholders and roles →

Which companies does HJELMÅS VVS AS own?

HJELMÅS VVS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HJELMÅS VVS AS

Who owns HJELMÅS VVS AS?

FÅVNE HOLDING AS is the largest registered owner, with 35.0%.

What is the revenue of HJELMÅS VVS AS?

HJELMÅS VVS AS had revenue of NOK 31.0m in 2024.

Who is the general manager of HJELMÅS VVS AS?

Linn Andvik Lahti is registered as general manager of HJELMÅS VVS AS.

Where is HJELMÅS VVS AS based?

HJELMÅS VVS AS has its business address in Eikangervåg.

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.