BIZTRAC BETA
Wholesale of other machinery and equipment

ARTEMIS AS

Org. no. 983409385 Limited company (AS) Oslo Incorporated 2001 Active
Ownership graph ↗
Revenue 2024 NOK 182,000
Operating profit NOK −206,000
Equity NOK −288,000
Incorporated 2001
Share capital NOK 750,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−288k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−206k kr).

ARTEMIS AS is registered as a limited company in Oslo, Oslo with organisation number 983409385. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2001. Registered share capital is NOK 750,000, divided into 7500 shares. The company's stated purpose is: “Handel med utstyr til jakt og våpen, samt naturlig tilhørende forretningsområder.”. The most recent filed accounts, for the 2024 financial year, show NOK 182,000 in revenue and NOK −206,000 in operating profit.

Key figures · 2024

Revenue
NOK 182,000
Operating profit
NOK −206,000
Equity
NOK −288,000

Financial health · 2024

Liquidity
1.22
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-24.0%
Weak
Equity as a share of total capital

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

Who owns ARTEMIS AS?

JAN CHRISTOPHER SOELBERG
ARTEMIS AS
NOK 182,000 rev. · NOK −206,000 profit

ARTEMIS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARTEMIS AS

Who owns ARTEMIS AS?

JAN CHRISTOPHER SOELBERG is the largest registered owner, with 86.7%.

What is the revenue of ARTEMIS AS?

ARTEMIS AS had revenue of NOK 182,000 in 2024.

Who is the general manager of ARTEMIS AS?

Jan Christopher Soelberg is registered as general manager of ARTEMIS AS.

Where is ARTEMIS AS based?

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