BIZTRAC BETA
Rental and operating of own or leased real estate

SIWA EIENDOM AS

Org. no. 880841602 Limited company (AS) Hustadvika Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 2,000
Operating profit NOK −13,000
Equity NOK 822,000
Incorporated 1999
Share capital NOK 129,000

Signals

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

SIWA EIENDOM AS is registered as a limited company in Hustadvika, Møre og Romsdal with organisation number 880841602. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 129,000, divided into 4024 shares. The company's stated purpose is: “Eie, drive og utvikle eiendom samt andre eventuelle fremtidige selskaper som kommer til eie.”. The most recent filed accounts, for the 2025 financial year, show NOK 2,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 2,000
Operating profit
NOK −13,000
Equity
NOK 822,000
Est. value
NOK 576,000

Financial health · 2025

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

Who owns SIWA EIENDOM AS?

ELDAR BJARNE SKOTHEIM
SIWA EIENDOM AS
NOK 2,000 rev. · NOK −13,000 profit

SIWA EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about SIWA EIENDOM AS

Who owns SIWA EIENDOM AS?

ELDAR BJARNE SKOTHEIM is the largest registered owner, with 44.7%.

What is the revenue of SIWA EIENDOM AS?

SIWA EIENDOM AS had revenue of NOK 2,000 in 2025.

Who is the general manager of SIWA EIENDOM AS?

Eldar Bjarne Skotheim is registered as general manager of SIWA EIENDOM AS.

Where is SIWA EIENDOM AS based?

SIWA EIENDOM AS has its business address in Farstad.

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.