biztrac. BETA
COMPANY REGISTER PROFILE
927857693 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Freight ocean transport

SONGA LEOPARD AS

Org. no. 927857693 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 USD 9.5m
Operating profit USD 8.3m
Equity USD 17.8m
Incorporated 2021
Share capital NOK 60,000

SONGA LEOPARD AS is registered as a limited company in Oslo, Oslo with organisation number 927857693. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2021. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Skipsrelatert virksomhet, herunder eie og drive skip, enten direkte  eller indirekte gjennom deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show USD 9.5m in revenue and USD 8.3m in operating profit.

This company reports in USD. The figures below are as filed, not converted to kroner. The top lists convert them to NOK at Norges Bank's rate for the end of the accounting year.

Key figures · 2025

Revenue
USD 9.5m
▲ +4 %
Operating profit
USD 8.3m
▲ +53 %
Equity
USD 17.8m
▲ +17 %
Est. value
NOK 315.2m

Financial health · 2025

Liquidity
1.56
Good
Current assets ÷ current liabilities
Profitability
26.9%
Very good
Return on total assets
Solidity
58.3%
Very good
Equity as a share of total capital

Who owns SONGA LEOPARD AS?

SONGA LEOPARD AS
NOK 9.5m rev. · NOK 8.3m profit

SONGA LEOPARD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SONGA LEOPARD AS

Who owns SONGA LEOPARD AS?

SONGA BOX HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SONGA LEOPARD AS?

SONGA LEOPARD AS had revenue of USD 9.5m in 2025.

Where is SONGA LEOPARD AS based?

SONGA LEOPARD 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.