biztrac. BETA
COMPANY REGISTER PROFILE
928130193 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 03.10.2026
⚠SELMER SUPRA III AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Freight ocean transport

SELMER SUPRA III AS

Org. no. 928130193 Limited company (AS) Oslo Incorporated 2021 In liquidation
Ownership graph ↗
Revenue 2025 NOK 46.7m
Operating profit NOK 4.7m
Equity NOK 85.4m
Incorporated 2021
Share capital NOK 18.7m

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

SELMER SUPRA III AS is registered as a limited company in Oslo, Oslo with organisation number 928130193. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2021. Registered share capital is NOK 18.7m, divided into 14997733 shares. The company's stated purpose is: “Kjøpe, eie og operere skipet MV "Aegir Selmer" ("Skipet"), og hva som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 46.7m in revenue and NOK 4.7m in operating profit.

Former names: SHIPINVEST 23 AS

Key figures · 2025

Revenue
NOK 46.7m
▲ +1 %
Operating profit
NOK 4.7m
▲ +134 %
Equity
NOK 85.4m
▲ +36 %

Financial health · 2025

Liquidity
2.13
Very good
Current assets ÷ current liabilities
Profitability
6.6%
Satisfactory
Return on total assets
Solidity
50.9%
Very good
Equity as a share of total capital

Who owns SELMER SUPRA III AS?

SELMER SUPRA III AS has 16 registered shareholders:

All shareholders and roles →

Frequently asked questions about SELMER SUPRA III AS

Who owns SELMER SUPRA III AS?

WEHR SCHIFFAHRTS GMBH & CO KG is the largest registered owner, with 21.7%.

What is the revenue of SELMER SUPRA III AS?

SELMER SUPRA III AS had revenue of NOK 46.7m in 2025.

Where is SELMER SUPRA III AS based?

SELMER SUPRA III 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.