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

SOLO HOLDING AS

Org. no. 932317117 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −24,000
Equity NOK 5.1m
Incorporated 2023
Share capital NOK 218,000

Signals

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

SOLO HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 932317117. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2023. Registered share capital is NOK 218,000, divided into 216 shares. The company's stated purpose is: “Eie aksjer og andeler i andre selskaper, samt det som står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −24,000
▲ +17 %
Equity
NOK 5.1m
▲ +10 %
Est. value
NOK 5.8m

Financial health · 2025

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

Who owns SOLO HOLDING AS?

SOLO HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SOLO HOLDING AS own?

SOLO HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SOLO HOLDING AS

Who owns SOLO HOLDING AS?

SOLFRID MALO is the largest registered owner, with 46.3%.

Where is SOLO HOLDING AS based?

SOLO HOLDING AS has its business address in Oslo.

Property

Business address c/o Solfrid Malo Jacob Hansens vei 17, 0370 Oslo
Cadastral unit 301-39/109/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.