BIZTRAC BETA
Business and other management consultancy activities

SOLVELL AS

Org. no. 981402952 Limited company (AS) Oslo Incorporated 1999 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −74,000
Equity NOK 53.9m
Incorporated 1999
Share capital NOK 710,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−74k kr).

SOLVELL AS is registered as a limited company in Oslo, Oslo with organisation number 981402952. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 1999. Registered share capital is NOK 710,000, divided into 4 shares. The company's stated purpose is: “Investeringsvirksomhet, herunder utvikling av prosjekter, deltagelse i andre selskaper og fast eiendom. Selskapet skal støtte allmennyttig virksomhet med kompetanse og kapital.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −74,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −74,000
Equity
NOK 53.9m
Est. value
NOK 55.7m

Financial health · 2024

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

Who owns SOLVELL AS?

ERIK MATHIAS BJERCKE LORENTZEN
SOLVELL AS
NOK 0 rev. · NOK −74,000 profit

SOLVELL AS has 4 registered shareholders:

All shareholders and roles →

Which companies does SOLVELL AS own?

SOLVELL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLVELL AS

Who owns SOLVELL AS?

ERIK MATHIAS BJERCKE LORENTZEN is the largest registered owner, with 25.0%.

What is the revenue of SOLVELL AS?

SOLVELL AS had revenue of NOK 0 in 2024.

Where is SOLVELL AS based?

SOLVELL AS has its business address in Oslo.

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.