BIZTRAC BETA
Rental and operating of own or leased real estate

SAMI SIIDA HOLDING AS

Org. no. 932215403 Limited company (AS) Kautokeino Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −53,000
Equity NOK −30,000
Incorporated 2023
Share capital NOK 1.2m

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−30k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−53k kr).
  • Nylig endring 2026-02-21 Aksjekapital registrert 2026-02-21.

SAMI SIIDA HOLDING AS is registered as a limited company in Kautokeino, Finnmark with organisation number 932215403. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 1.2m, divided into 4042 shares. The company's stated purpose is: “Å jobbe med samisk kulturformidling og utvikle samisk reiseliv. Selskapets formål er også drift av eiendomsmasse til Sami Siida Eiendom AS.”.

Key figures · 2024

Operating profit
NOK −53,000
Equity
NOK −30,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-2.7%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns SAMI SIIDA HOLDING AS?

AHW HOLDING AS
SAMI SIIDA HOLDING AS
· NOK −53,000 profit

SAMI SIIDA HOLDING AS has 11 registered shareholders:

All shareholders and roles →

Which companies does SAMI SIIDA HOLDING AS own?

SAMI SIIDA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SAMI SIIDA HOLDING AS

Who owns SAMI SIIDA HOLDING AS?

AHW HOLDING AS is the largest registered owner, with 34.0%.

Where is SAMI SIIDA HOLDING AS based?

SAMI SIIDA HOLDING AS has its business address in Kautokeino.

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.