BIZTRAC BETA
Freight ocean transport

APEX NORDIC DEAL 1 AS

Org. no. 925654485 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −18,000
Equity NOK 3.6m
Incorporated 2020
Share capital NOK 3.7m

Signals

3 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−18k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-02-01 Adresseendring registrert 2026-02-01.

APEX NORDIC DEAL 1 AS is registered as a limited company in Oslo, Oslo with organisation number 925654485. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2020. Registered share capital is NOK 3.7m, divided into 3719602 shares. The company's stated purpose is: “Investere i fond og aksjer og annet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 3.6m
Est. value
NOK 3.9m

Financial health · 2024

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

Who owns APEX NORDIC DEAL 1 AS?

SONGA CAPITAL AS
APEX NORDIC DEAL 1 AS
NOK 0 rev. · NOK −18,000 profit

APEX NORDIC DEAL 1 AS has 11 registered shareholders:

All shareholders and roles →

Frequently asked questions about APEX NORDIC DEAL 1 AS

Who owns APEX NORDIC DEAL 1 AS?

SONGA CAPITAL AS is the largest registered owner, with 57.5%.

What is the revenue of APEX NORDIC DEAL 1 AS?

APEX NORDIC DEAL 1 AS had revenue of NOK 0 in 2024.

Where is APEX NORDIC DEAL 1 AS based?

APEX NORDIC DEAL 1 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.