BIZTRAC BETA
Plumbing installation

HOLE VVS AS

Org. no. 999540708 Limited company (AS) Alver Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 4.2m
Operating profit NOK 155,000
Equity NOK −1.3m
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).

HOLE VVS AS is registered as a limited company in Alver, Vestland with organisation number 999540708. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive med rørleggervirksomhet, samt andre aktiviteter som naturlig har sammenheng med dette. Selskapet vil også ta del i andre selskaper, herunder også investering i aksjer og andeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.2m in revenue and NOK 155,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.2m
Operating profit
NOK 155,000
Equity
NOK −1.3m
Est. value
NOK 1.0m

Financial health · 2024

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

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

Who owns HOLE VVS AS?

ODD HEINE HOLE
HOLE VVS AS
NOK 4.2m rev. · NOK 155,000 profit

HOLE VVS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HOLE VVS AS

Who owns HOLE VVS AS?

ODD HEINE HOLE is the largest registered owner, with 100.0%.

What is the revenue of HOLE VVS AS?

HOLE VVS AS had revenue of NOK 4.2m in 2024.

Who is the general manager of HOLE VVS AS?

Odd Heine Hole is registered as general manager of HOLE VVS AS.

Where is HOLE VVS AS based?

HOLE VVS AS has its business address in Sæbøvågen.

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.