BIZTRAC BETA
Freight transport by road

OBINNA TRANSPORT AS

Org. no. 913629213 Limited company (AS) Oslo Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 15.7m
Operating profit NOK 1.8m
Equity NOK 6.6m
Incorporated 2014
Share capital NOK 30,000

OBINNA TRANSPORT AS is registered as a limited company in Oslo, Oslo with organisation number 913629213. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Transport av varer (godstransport på vei), samt tilknyttet virksomhet samt alt annet som naturlig hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 15.7m in revenue and NOK 1.8m in operating profit.

Key figures · 2024

Revenue
NOK 15.7m
Operating profit
NOK 1.8m
Equity
NOK 6.6m
Est. value
NOK 10.2m

Financial health · 2024

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

Who owns OBINNA TRANSPORT AS?

CHRISTIAN OKORO EZE
OBINNA TRANSPORT AS
NOK 15.7m rev. · NOK 1.8m profit

OBINNA TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OBINNA TRANSPORT AS own?

OBINNA TRANSPORT AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OBINNA TRANSPORT AS

Who owns OBINNA TRANSPORT AS?

CHRISTIAN OKORO EZE is the largest registered owner, with 100.0%.

What is the revenue of OBINNA TRANSPORT AS?

OBINNA TRANSPORT AS had revenue of NOK 15.7m in 2024.

Who is the general manager of OBINNA TRANSPORT AS?

Christian Okoro Eze is registered as general manager of OBINNA TRANSPORT AS.

Where is OBINNA TRANSPORT AS based?

OBINNA TRANSPORT 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.