BIZTRAC BETA
Combined facilities support activities

SØ KOMP AS

Org. no. 933033902 Limited company (AS) Ørsta Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 678,000
Operating profit NOK −4,000
Equity NOK 19,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

SØ KOMP AS is registered as a limited company in Ørsta, Møre og Romsdal with organisation number 933033902. The business is classified under combined facilities support activities (NACE 81.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby vaktmestertjenester, inkludert, men ikke begrenset til, vedlikehold av eiendom, mindre reparasjoner, gartnerarbeid, og andre relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 678,000 in revenue and NOK −4,000 in operating profit.

Key figures · 2024

Revenue
NOK 678,000
Operating profit
NOK −4,000
Equity
NOK 19,000
Est. value
NOK 439,000

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.3%
Weak
Equity as a share of total capital

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

Who owns SØ KOMP AS?

SVEINAR ØVRELID
SØ KOMP AS
NOK 678,000 rev. · NOK −4,000 profit

SØ KOMP AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SØ KOMP AS own?

SØ KOMP AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØ KOMP AS

Who owns SØ KOMP AS?

SVEINAR ØVRELID is the largest registered owner, with 100.0%.

What is the revenue of SØ KOMP AS?

SØ KOMP AS had revenue of NOK 678,000 in 2024.

Where is SØ KOMP AS based?

SØ KOMP AS has its business address in Ørsta.

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.