BIZTRAC BETA
Uoppgitt

SOLEMA HOLDING AS

Org. no. 920259952 Limited company (AS) Frosta Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 58,000
Operating profit NOK −47,000
Equity NOK 174,000
Incorporated 2018
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−47k kr).

SOLEMA HOLDING AS is registered as a limited company in Frosta, Trøndelag with organisation number 920259952. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investere i aksjer og andeler i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 58,000 in revenue and NOK −47,000 in operating profit.

Key figures · 2025

Revenue
NOK 58,000
Operating profit
NOK −47,000
Equity
NOK 174,000
Est. value
NOK 128,000

Financial health · 2025

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

Who owns SOLEMA HOLDING AS?

SIV TONE FAANES
SOLEMA HOLDING AS
NOK 58,000 rev. · NOK −47,000 profit

SOLEMA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLEMA HOLDING AS own?

SOLEMA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLEMA HOLDING AS

Who owns SOLEMA HOLDING AS?

SIV TONE FAANES is the largest registered owner, with 100.0%.

What is the revenue of SOLEMA HOLDING AS?

SOLEMA HOLDING AS had revenue of NOK 58,000 in 2025.

Who is the general manager of SOLEMA HOLDING AS?

Siv Tone Faanes is registered as general manager of SOLEMA HOLDING AS.

Where is SOLEMA HOLDING AS based?

SOLEMA HOLDING AS has its business address in Frosta.

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.