BIZTRAC BETA
Uoppgitt

HSMHOLDING AS

Org. no. 933863565 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −35
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−35 kr).

HSMHOLDING AS is registered as a limited company in Drammen, Buskerud with organisation number 933863565. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper, samt hva herved naturlig står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −35 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −35
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2024

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

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

Who owns HSMHOLDING AS?

HÅVARD SKILLE MIDTGÅRD
HSMHOLDING AS
NOK 0 rev. · NOK −35 profit

HSMHOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HSMHOLDING AS own?

HSMHOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HSMHOLDING AS

Who owns HSMHOLDING AS?

HÅVARD SKILLE MIDTGÅRD is the largest registered owner, with 100.0%.

What is the revenue of HSMHOLDING AS?

HSMHOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of HSMHOLDING AS?

Håvard Skille Midtgård is registered as general manager of HSMHOLDING AS.

Where is HSMHOLDING AS based?

HSMHOLDING AS has its business address in Drammen.

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.