BIZTRAC BETA
Electrical installation

H-TECH AS

Org. no. 812891642 Limited company (AS) Øvre Eiker Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −29,000
Equity NOK 23.7m
Incorporated 2013
Share capital NOK 30,000

Signals

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

H-TECH AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 812891642. The business is classified under electrical installation (NACE 43.210). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Handel, håndverks - og servicevirksomhet og annet som naturlig faller sammen med dette. Kjøp, salg og drift av fast eiendom, samt ved aksjer eller på annen måte investere i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −29,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −29,000
Equity
NOK 23.7m
Est. value
NOK 36.5m

Financial health · 2024

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

Who owns H-TECH AS?

ALMIR HAMZIC
H-TECH AS
NOK 0 rev. · NOK −29,000 profit

H-TECH AS has 2 registered shareholders:

All shareholders and roles →

Which companies does H-TECH AS own?

H-TECH AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about H-TECH AS

Who owns H-TECH AS?

ALMIR HAMZIC is the largest registered owner, with 50.0%.

What is the revenue of H-TECH AS?

H-TECH AS had revenue of NOK 0 in 2024.

Who is the general manager of H-TECH AS?

Almir Hamzic is registered as general manager of H-TECH AS.

Where is H-TECH AS based?

H-TECH AS has its business address in Hokksund.

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.