BIZTRAC BETA
Business and other management consultancy activities

SORIAK AS

Org. no. 916474938 Limited company (AS) Tana Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 145,000
Operating profit NOK −126,000
Equity NOK 5.2m
Incorporated 2015
Share capital NOK 310,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−126k kr).
  • Nylig endring 2026-04-09 Adresseendring registrert 2026-04-09.

SORIAK AS is registered as a limited company in Tana, Finnmark with organisation number 916474938. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2015. Registered share capital is NOK 310,000, divided into 61180 shares. The company's stated purpose is: “Drive virksomhet innenfor utvikling og investering i andre selskaper og alt som står i forbindelse med de forannevnte virksomheter.”. The most recent filed accounts, for the 2024 financial year, show NOK 145,000 in revenue and NOK −126,000 in operating profit.

Key figures · 2024

Revenue
NOK 145,000
Operating profit
NOK −126,000
Equity
NOK 5.2m
Est. value
NOK 8.5m

Financial health · 2024

Liquidity
36.11
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
85.3%
Very good
Equity as a share of total capital

Who owns SORIAK AS?

INGVILD SYNNØVE SNOW
SORIAK AS
NOK 145,000 rev. · NOK −126,000 profit

SORIAK AS has 14 registered shareholders:

All shareholders and roles →

Which companies does SORIAK AS own?

SORIAK AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SORIAK AS

Who owns SORIAK AS?

INGVILD SYNNØVE SNOW is the largest registered owner, with 56.2%.

What is the revenue of SORIAK AS?

SORIAK AS had revenue of NOK 145,000 in 2024.

Where is SORIAK AS based?

SORIAK AS has its business address in Sirma.

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.