BIZTRAC BETA
Buying and selling of own real estate

HA-MS AS

Org. no. 992122447 Limited company (AS) Drammen Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 3,000
Operating profit NOK −15,000
Equity NOK 12.8m
Incorporated 2007
Share capital NOK 100,000

Signals

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

HA-MS AS is registered as a limited company in Drammen, Buskerud with organisation number 992122447. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2007. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive med investering i fast eiendom, herunder utleie, samt kjøp og salg av verdipapir og løsøre, og annen drift som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 3,000 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 3,000
Operating profit
NOK −15,000
Equity
NOK 12.8m
Est. value
NOK 12.4m

Financial health · 2024

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

Who owns HA-MS AS?

STEIN INGE ERIKSEN
HA-MS AS
NOK 3,000 rev. · NOK −15,000 profit

HA-MS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HA-MS AS own?

HA-MS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HA-MS AS

Who owns HA-MS AS?

STEIN INGE ERIKSEN is the largest registered owner, with 100.0%.

What is the revenue of HA-MS AS?

HA-MS AS had revenue of NOK 3,000 in 2024.

Who is the general manager of HA-MS AS?

Stein Inge Eriksen is registered as general manager of HA-MS AS.

Where is HA-MS AS based?

HA-MS AS has its business address in Solbergelva.

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.