BIZTRAC BETA
COMPANY REGISTER PROFILE
826118822 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

SOLUS AS

Org. no. 826118822 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Operating profit NOK −111,000
Equity NOK 17.6m
Incorporated 2020
Share capital NOK 220,000

Signals

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

SOLUS AS is registered as a limited company in Stavanger, Rogaland with organisation number 826118822. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2020. Registered share capital is NOK 220,000, divided into 100 shares. The company's stated purpose is: “Investering i aksjer.”.

Key figures · 2025

Operating profit
NOK −111,000
▼ −21 %
Equity
NOK 17.6m
▲ +15 %
Est. value
NOK 24.2m

Financial health · 2025

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

Who owns SOLUS AS?

SOLUS AS
· NOK −111,000 profit

SOLUS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLUS AS own?

SOLUS AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SOLUS AS

Who owns SOLUS AS?

KJELL JOAR VIE is the largest registered owner, with 100.0%.

Where is SOLUS AS based?

SOLUS AS has its business address in Stavanger.

Property

Business address c/o Kjell Joar Vie Dykjelsletta 4, 4032 Stavanger
Cadastral unit 1103-14/1089/0/0
Building Enebolig · 1 unit

2 companies are registered at this address.

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.