BIZTRAC BETA
Freight ocean transport

MPC ECOBOX OPCO 4 AS

Org. no. 829047632 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 11.4m
Operating profit NOK 6.5m
Equity NOK −82,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−82k kr).

MPC ECOBOX OPCO 4 AS is registered as a limited company in Bærum, Akershus with organisation number 829047632. The business is classified under freight ocean transport (NACE 50.201). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Delta i skipsfartsvirksomhet, herunder eierskap, drift, handel og investering i skip, verdipapirer og andre formuesobjekter, samt deltakelse i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.4m in revenue and NOK 6.5m in operating profit.

Key figures · 2024

Revenue
NOK 11.4m
Operating profit
NOK 6.5m
Equity
NOK −82,000
Est. value
NOK 28.3m

Financial health · 2024

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

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

Who owns MPC ECOBOX OPCO 4 AS?

OCEAN YIELD AS
MPC ECOBOX OPCO 4 AS
NOK 11.4m rev. · NOK 6.5m profit

MPC ECOBOX OPCO 4 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MPC ECOBOX OPCO 4 AS

Who owns MPC ECOBOX OPCO 4 AS?

OCEAN YIELD AS is the largest registered owner, with 100.0%.

What is the revenue of MPC ECOBOX OPCO 4 AS?

MPC ECOBOX OPCO 4 AS had revenue of NOK 11.4m in 2024.

Where is MPC ECOBOX OPCO 4 AS based?

MPC ECOBOX OPCO 4 AS has its business address in Lysaker.

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.