BIZTRAC BETA
Passenger ocean transport

HX SHOREX AS

Org. no. 923471928 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −8,000
Equity NOK −36,000
Incorporated 2019
Share capital NOK 30,000

Signals

4 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−36k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−8k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-04-22 Adresseendring registrert 2026-04-22.

HX SHOREX AS is registered as a limited company in Oslo, Oslo with organisation number 923471928. The business is classified under passenger ocean transport (NACE 50.101). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i andre selskaper som driver transport- og reiselivsvirksomhet og dermed tilknyttet virksomhet, herunder skipsfart og offshorevirksomhet, samt investeringer og deltakelse i andre selskaper.”.

Key figures · 2024

Operating profit
NOK −8,000
Equity
NOK −36,000

Financial health · 2024

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

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

Who owns HX SHOREX AS?

HURTIGRUTEN EXPEDITIONS AS
HX SHOREX AS
· NOK −8,000 profit

HX SHOREX AS has 1 registered shareholder:

All shareholders and roles →

Group structure

HX SHOREX AS er morselskap for 5 datterselskaper:

Frequently asked questions about HX SHOREX AS

Who owns HX SHOREX AS?

HURTIGRUTEN EXPEDITIONS AS is the largest registered owner, with 100.0%.

Where is HX SHOREX AS based?

HX SHOREX 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.