BIZTRAC BETA
Visual arts creation activities

GALLERI SOS AS

Org. no. 817397352 Limited company (AS) Vefsn Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.5m
Operating profit NOK −117,000
Equity NOK −599,000
Incorporated 2016
Share capital NOK 33,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−599k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−117k kr).

GALLERI SOS AS is registered as a limited company in Vefsn, Nordland with organisation number 817397352. The business is classified under visual arts creation activities (NACE 90.120). The company was incorporated in 2016. Registered share capital is NOK 33,000, divided into 30 shares. The company's stated purpose is: “Egenproduksjon av kunst, illustrasjoner, design, drift av eget galleri samt markedsføring.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.5m in revenue and NOK −117,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.5m
Operating profit
NOK −117,000
Equity
NOK −599,000

Financial health · 2025

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

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

Who owns GALLERI SOS AS?

STIG OVE SIVERTSEN
GALLERI SOS AS
NOK 1.5m rev. · NOK −117,000 profit

GALLERI SOS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about GALLERI SOS AS

Who owns GALLERI SOS AS?

STIG OVE SIVERTSEN is the largest registered owner, with 50.0%.

What is the revenue of GALLERI SOS AS?

GALLERI SOS AS had revenue of NOK 1.5m in 2024.

Who is the general manager of GALLERI SOS AS?

Marit Sivertsen is registered as general manager of GALLERI SOS AS.

Where is GALLERI SOS AS based?

GALLERI SOS AS has its business address in Mosjøen.

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.