BIZTRAC BETA
COMPANY REGISTER PROFILE
999237983 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Uoppgitt

ARCTIC ORTUS AS

Org. no. 999237983 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Operating profit NOK −101,000
Equity NOK 433,000
Incorporated 2012
Share capital NOK 660,000

Signals

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

ARCTIC ORTUS AS is registered as a limited company in Oslo, Oslo with organisation number 999237983. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 660,000, divided into 6600 shares. The company's stated purpose is: “Å investere i og finansiere andre selskaper, samt virksomhet som står i naturlig forbindelse hermed.”.

Former names: ARCTIC PROSJEKT 12 AS

Key figures · 2025

Operating profit
NOK −101,000
▼ −68 %
Equity
NOK 433,000
▼ −5 %
Est. value
NOK 509,000

Financial health · 2025

Liquidity
327.34
Very good
Current assets ÷ current liabilities
Profitability
-20.8%
Not satisfactory
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns ARCTIC ORTUS AS?

ARCTIC ORTUS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ARCTIC ORTUS AS

Who owns ARCTIC ORTUS AS?

ARCTIC SECURITIES AS is the largest registered owner, with 50.0%.

Where is ARCTIC ORTUS AS based?

ARCTIC ORTUS AS has its business address in Oslo.

Property

Business address Haakon VIIs gate 5, 0161 Oslo
Cadastral unit 301-209/130/0/0

255 companies are registered at this address.

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.