BIZTRAC BETA
Other business support service activities n.e.c.

SINONORDIC AS

Org. no. 989689045 Limited company (AS) Kristiansand Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −13,000
Equity NOK 5.9m
Incorporated 2006
Share capital NOK 6.4m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−13k kr).
  • Nylig endring 2026-02-06 Adresseendring registrert 2026-02-06.

SINONORDIC AS is registered as a limited company in Kristiansand, Agder with organisation number 989689045. The business is classified under other business support service activities n.e.c. (NACE 82.990). The company was incorporated in 2006. Registered share capital is NOK 6.4m, divided into 6400 shares. The company's stated purpose is: “Konsulentvirksomhet innen salg og markedsføring, kjøp og salg av industrivarer, herunder import og eksport av slike selv, eller gjennom hel- eller deleide selskaper eller ved samarbeide med andre virksomheter, samt annen forvaltning, herunder eiendomsinvesteringer og utleie av fast eiendom. Dessuten ved aksjekjøp eller på annen måte deltakelse i andre foretak.”.

Key figures · 2024

Operating profit
NOK −13,000
Equity
NOK 5.9m
Est. value
NOK 8.5m

Financial health · 2024

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

Who owns SINONORDIC AS?

JIAPENG WANG
SINONORDIC AS
· NOK −13,000 profit

SINONORDIC AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SINONORDIC AS own?

SINONORDIC AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SINONORDIC AS

Who owns SINONORDIC AS?

JIAPENG WANG is the largest registered owner, with 100.0%.

Where is SINONORDIC AS based?

SINONORDIC AS has its business address in Kristiansand S.

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.