BIZTRAC BETA
Wholesale of motor vehicles

ARCTIC-NB AS

Org. no. 820882512 Limited company (AS) Nesbyen Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −10,000
Equity NOK −52,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−52k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).

ARCTIC-NB AS is registered as a limited company in Nesbyen, Buskerud with organisation number 820882512. The business is classified under wholesale of motor vehicles (NACE 46.710). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Formidling og salg av importerte busser og andre produkter/tjenester som naturlig hører sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, samt kjøp og salg av aksjer og på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −10,000
Equity
NOK −52,000

Financial health · 2025

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3093.6%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns ARCTIC-NB AS?

MARCIN MORTY KAJDA
ARCTIC-NB AS
· NOK −10,000 profit

ARCTIC-NB AS has 2 registered shareholders:

All shareholders and roles →

Which companies does ARCTIC-NB AS own?

ARCTIC-NB AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ARCTIC-NB AS

Who owns ARCTIC-NB AS?

MARCIN MORTY KAJDA is the largest registered owner, with 80.0%.

Who is the general manager of ARCTIC-NB AS?

Marcin Morty Kajda is registered as general manager of ARCTIC-NB AS.

Where is ARCTIC-NB AS based?

ARCTIC-NB AS has its business address in Nesbyen.

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.