BIZTRAC BETA
Development of building projects

SSH EIENDOMSUTVIKLING AS

Org. no. 920397557 Limited company (AS) Gjemnes Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −25,000
Equity NOK 1.7m
Incorporated 2017
Share capital NOK 630,000

Signals

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

SSH EIENDOMSUTVIKLING AS is registered as a limited company in Gjemnes, Møre og Romsdal with organisation number 920397557. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2017. Registered share capital is NOK 630,000, divided into 300 shares. The company's stated purpose is: “Eindomsutvikling, herunder deltagelse i virksomheter med tilsvarende formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 1.7m
Est. value
NOK 1.2m

Financial health · 2024

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

Who owns SSH EIENDOMSUTVIKLING AS?

ATLE HOEM
SSH EIENDOMSUTVIKLING AS
NOK 0 rev. · NOK −25,000 profit

SSH EIENDOMSUTVIKLING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about SSH EIENDOMSUTVIKLING AS

Who owns SSH EIENDOMSUTVIKLING AS?

ATLE HOEM is the largest registered owner, with 33.3%.

What is the revenue of SSH EIENDOMSUTVIKLING AS?

SSH EIENDOMSUTVIKLING AS had revenue of NOK 0 in 2024.

Who is the general manager of SSH EIENDOMSUTVIKLING AS?

Nils Arild Sæther is registered as general manager of SSH EIENDOMSUTVIKLING AS.

Where is SSH EIENDOMSUTVIKLING AS based?

SSH EIENDOMSUTVIKLING AS has its business address in Batnfjordsøra.

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.