BIZTRAC BETA
Other business support service activities n.e.c.

HMS HOLDING AS

Org. no. 985174342 Limited company (AS) Bergen Incorporated 2002 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −716,000
Equity NOK 14.7m
Incorporated 2002
Share capital NOK 1.0m

Signals

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

HMS HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 985174342. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2002. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Konsulentvirksomhet, handelsvirksomhet og investeringsvirksomhet, herunder i aksjer og andre verdipapirer samt eie og drive fast eiendom og alt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −716,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −716,000
Equity
NOK 14.7m
Est. value
NOK 12.4m

Financial health · 2024

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

Who owns HMS HOLDING AS?

HELGE MARTIN STOKKE
HMS HOLDING AS
NOK 0 rev. · NOK −716,000 profit

HMS HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HMS HOLDING AS own?

HMS HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HMS HOLDING AS

Who owns HMS HOLDING AS?

HELGE MARTIN STOKKE is the largest registered owner, with 100.0%.

What is the revenue of HMS HOLDING AS?

HMS HOLDING AS had revenue of NOK 0 in 2024.

Where is HMS HOLDING AS based?

HMS HOLDING AS has its business address in Bergen.

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.