BIZTRAC BETA
Uoppgitt

SIUTA SOWA HOLDING AS

Org. no. 933477533 Limited company (AS) Indre Østfold Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −6,000
Equity NOK 24,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

SIUTA SOWA HOLDING AS is registered as a limited company in Indre Østfold, Østfold with organisation number 933477533. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investering i andre selskaper og alt som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −6,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −6,000
Equity
NOK 24,000
Est. value
NOK 28,000

Financial health · 2025

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

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

Who owns SIUTA SOWA HOLDING AS?

ALEKSANDRA EWA SOWA-SIUTA
SIUTA SOWA HOLDING AS
NOK 0 rev. · NOK −6,000 profit

SIUTA SOWA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SIUTA SOWA HOLDING AS own?

SIUTA SOWA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SIUTA SOWA HOLDING AS

Who owns SIUTA SOWA HOLDING AS?

ALEKSANDRA EWA SOWA-SIUTA is the largest registered owner, with 50.0%.

What is the revenue of SIUTA SOWA HOLDING AS?

SIUTA SOWA HOLDING AS had revenue of NOK 0 in 2025.

Where is SIUTA SOWA HOLDING AS based?

SIUTA SOWA HOLDING AS has its business address in Trøgstad.

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.