BIZTRAC BETA
Photographic activities

SØRMO HOLDING AS

Org. no. 924753080 Limited company (AS) Stord Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 24,000
Incorporated 2020
Share capital NOK 30,000

SØRMO HOLDING AS is registered as a limited company in Stord, Vestland with organisation number 924753080. The business is classified under photographic activities (NACE 74.200). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 24,000
Est. value
NOK 40,000

Financial health · 2025

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

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

Who owns SØRMO HOLDING AS?

STIG BIRGER SÆTREVIK SØRMO
SØRMO HOLDING AS
NOK 0 rev. · NOK 0 profit

SØRMO HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SØRMO HOLDING AS own?

SØRMO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØRMO HOLDING AS

Who owns SØRMO HOLDING AS?

STIG BIRGER SÆTREVIK SØRMO is the largest registered owner, with 100.0%.

What is the revenue of SØRMO HOLDING AS?

SØRMO HOLDING AS had revenue of NOK 0 in 2025.

Where is SØRMO HOLDING AS based?

SØRMO HOLDING AS has its business address in Stord.

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.