BIZTRAC BETA
COMPANY REGISTER PROFILE
921373384 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

SOLSKOG AS

Org. no. 921373384 Limited company (AS) Stavanger Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 728,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

SOLSKOG AS is registered as a limited company in Stavanger, Rogaland with organisation number 921373384. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Investering.”.

Key figures · 2025

Operating profit
NOK −13,000
▼ −13 %
Equity
NOK 728,000
▲ +18 %
Est. value
NOK 801,000

Financial health · 2025

Liquidity
173.20
Very good
Current assets ÷ current liabilities
Profitability
19.7%
Very good
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns SOLSKOG AS?

SOLSKOG AS
· NOK −13,000 profit

SOLSKOG AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SOLSKOG AS own?

SOLSKOG AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLSKOG AS

Who owns SOLSKOG AS?

PETTER SKOGHEIM is the largest registered owner, with 100.0%.

Where is SOLSKOG AS based?

SOLSKOG AS has its business address in Stavanger.

Property

Business address Jelsagata 81, 4012 Stavanger
Cadastral unit 1103-54/375/0/0
Building Enebolig · 1 unit

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.