BIZTRAC BETA
Other postal and courier activities

DIWAN TRANSPORT AS

Org. no. 921152884 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 68,000
Equity NOK −3,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

DIWAN TRANSPORT AS is registered as a limited company in Oslo, Oslo with organisation number 921152884. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Distribusjonskjøring, transport med lastebil som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 68,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 68,000
Equity
NOK −3,000
Est. value
NOK 419,000

Financial health · 2025

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

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

Who owns DIWAN TRANSPORT AS?

NABEEL KADHIM DIWAN DIWAN
DIWAN TRANSPORT AS
NOK 0 rev. · NOK 68,000 profit

DIWAN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DIWAN TRANSPORT AS

Who owns DIWAN TRANSPORT AS?

NABEEL KADHIM DIWAN DIWAN is the largest registered owner, with 100.0%.

What is the revenue of DIWAN TRANSPORT AS?

DIWAN TRANSPORT AS had revenue of NOK 0 in 2025.

Who is the general manager of DIWAN TRANSPORT AS?

Nabeel Kadhim Diwan Diwan is registered as general manager of DIWAN TRANSPORT AS.

Where is DIWAN TRANSPORT AS based?

DIWAN 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.