biztrac. BETA
COMPANY REGISTER PROFILE
989119206 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Wholesale of mining, construction and civil engineering machinery

S.H.S EIENDOM HOLDING AS

Org. no. 989119206 Limited company (AS) Bergen Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −54,000
Equity NOK 814,000
Incorporated 2005
Share capital NOK 559,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−54k kr).
  • Nylig endring 2026-07-31 Adresseendring registrert 2026-07-31.

S.H.S EIENDOM HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 989119206. The business is classified under wholesale of mining, construction and civil engineering machinery (NACE 46.630). The company was incorporated in 2005. Registered share capital is NOK 559,000, divided into 559 shares. The company's stated purpose is: “Investere i finans- og realobjekter samt drive utleie av fast eiendom.”.

Former names: STEINAR H. SUNDE HOLDING AS

Key figures · 2025

Operating profit
NOK −54,000
▼ −57 %
Equity
NOK 814,000
▼ −58 %
Est. value
NOK 20.9m

Financial health · 2025

Liquidity
1.07
Satisfactory
Current assets ÷ current liabilities
Profitability
90.8%
Very good
Return on total assets
Solidity
23.2%
Good
Equity as a share of total capital

Who owns S.H.S EIENDOM HOLDING AS?

S.H.S EIENDOM HOLDING AS
· NOK −54,000 profit

S.H.S EIENDOM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does S.H.S EIENDOM HOLDING AS own?

S.H.S EIENDOM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about S.H.S EIENDOM HOLDING AS

Who owns S.H.S EIENDOM HOLDING AS?

Steinar Helge Sunde is the largest registered owner, with 100.0%.

Where is S.H.S EIENDOM HOLDING AS based?

S.H.S EIENDOM HOLDING AS has its business address in Rådal.

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.