biztrac. BETA
COMPANY REGISTER PROFILE
933674975 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Construction of residential and non-residential buildings

H3 DRIFT OG BYGG AS

Org. no. 933674975 Limited company (AS) Hadsel Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −831
Equity NOK 23,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−831 kr).
  • Nylig endring 2026-08-05 Adresseendring registrert 2026-08-05.

H3 DRIFT OG BYGG AS is registered as a limited company in Hadsel, Nordland with organisation number 933674975. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby tømrertjenester, snekkertjenester, malertjenester - samt drift og fremleie av fritidsboliger og boliger, inkludert korttidsleie.”.

Key figures · 2025

Operating profit
NOK −831
Equity
NOK 23,000
▼ −3 %
Est. value
NOK 24,000

Financial health · 2025

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

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

Who owns H3 DRIFT OG BYGG AS?

H3 DRIFT OG BYGG AS
· NOK −831 profit

H3 DRIFT OG BYGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about H3 DRIFT OG BYGG AS

Who owns H3 DRIFT OG BYGG AS?

Tore Nysæter is the largest registered owner, with 100.0%.

Who is the general manager of H3 DRIFT OG BYGG AS?

Cato Harry Jenssen is registered as general manager of H3 DRIFT OG BYGG AS.

Where is H3 DRIFT OG BYGG AS based?

H3 DRIFT OG BYGG AS has its business address in Stokmarknes.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.