BIZTRAC BETA
Other captive investment companies

SOMA HOLDING AS

Org. no. 917524858 Limited company (AS) Kautokeino Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 132,000
Operating profit NOK 81,000
Equity NOK −921,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−921k kr).

SOMA HOLDING AS is registered as a limited company in Kautokeino, Finnmark with organisation number 917524858. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Hovedkontortjenester og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 132,000 in revenue and NOK 81,000 in operating profit.

Key figures · 2025

Revenue
NOK 132,000
Operating profit
NOK 81,000
Equity
NOK −921,000
Est. value
NOK 508,000

Financial health · 2025

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

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

Who owns SOMA HOLDING AS?

SØLVI RAGNVEIG BONGO
SOMA HOLDING AS
NOK 132,000 rev. · NOK 81,000 profit

SOMA HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SOMA HOLDING AS own?

SOMA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOMA HOLDING AS

Who owns SOMA HOLDING AS?

SØLVI RAGNVEIG BONGO is the largest registered owner, with 50.0%.

What is the revenue of SOMA HOLDING AS?

SOMA HOLDING AS had revenue of NOK 132,000 in 2025.

Where is SOMA HOLDING AS based?

SOMA HOLDING AS has its business address in Kautokeino.

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.