BIZTRAC BETA
Rental and leasing of water transport equipment

POLARXPLORER AS

Org. no. 928138895 Limited company (AS) Svalbard Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 9.4m
Operating profit NOK −1.1m
Equity NOK 2.5m
Incorporated 2021
Share capital NOK 1.0m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,1 mill kr).
  • Nylig endring 2026-07-22 Aksjekapital registrert 2026-07-22.

POLARXPLORER AS is registered as a limited company in Svalbard, Svalbard with organisation number 928138895. The business is classified under rental and leasing of water transport equipment (NACE 77.340). The company was incorporated in 2021. Registered share capital is NOK 1.0m, divided into 1000000 shares. The company's stated purpose is: “Eie å drifte fartøy RV Polarxplorer, samt virksomhet som står i naturlig forbindelse med, herunder, men ikke begrenset til å investere i tilknyttet eller tilsvarende selskap eller virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.4m in revenue and NOK −1.1m in operating profit.

Key figures · 2024

Revenue
NOK 9.4m
Operating profit
NOK −1.1m
Equity
NOK 2.5m
Est. value
NOK 7.2m

Financial health · 2024

Liquidity
1.39
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
62.7%
Very good
Equity as a share of total capital

Who owns POLARXPLORER AS?

KVITBJØRN AS
POLARXPLORER AS
NOK 9.4m rev. · NOK −1.1m profit

POLARXPLORER AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about POLARXPLORER AS

Who owns POLARXPLORER AS?

KVITBJØRN AS is the largest registered owner, with 50.0%.

What is the revenue of POLARXPLORER AS?

POLARXPLORER AS had revenue of NOK 9.4m in 2024.

Where is POLARXPLORER AS based?

POLARXPLORER AS has its business address in Longyearbyen.

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.