BIZTRAC BETA
Retail sale of other food

SOLSONE AS

Org. no. 912435717 Limited company (AS) Oslo Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 12.9m
Operating profit NOK −113,000
Equity NOK 459,000
Incorporated 2013
Employees 5
Share capital NOK 60,000

Signals

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

SOLSONE AS is registered as a limited company in Oslo, Oslo with organisation number 912435717. The business is classified under retail sale of other food (NACE 47.270). The company was incorporated in 2013 and has 5 registered employees. Registered share capital is NOK 60,000, divided into 300 shares. The company's stated purpose is: “Fremstilling/salg av gaver og råvarer og andre produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender.”. The most recent filed accounts, for the 2024 financial year, show NOK 12.9m in revenue and NOK −113,000 in operating profit.

Key figures · 2024

Revenue
NOK 12.9m
Operating profit
NOK −113,000
Equity
NOK 459,000
Est. value
NOK 2.5m

Financial health · 2024

Liquidity
1.06
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.1%
Satisfactory
Equity as a share of total capital

Who owns SOLSONE AS?

KAI YAO
SOLSONE AS
NOK 12.9m rev. · NOK −113,000 profit

SOLSONE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SOLSONE AS

Who owns SOLSONE AS?

KAI YAO is the largest registered owner, with 100.0%.

What is the revenue of SOLSONE AS?

SOLSONE AS had revenue of NOK 12.9m in 2024.

Who is the general manager of SOLSONE AS?

Kai Yao is registered as general manager of SOLSONE AS.

Where is SOLSONE AS based?

SOLSONE 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.