BIZTRAC BETA
Freight transport by road

METI TRANSPORT AS

Org. no. 934377389 Limited company (AS) Drammen Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 163,000
Operating profit NOK 17,000
Equity NOK 39,000
Incorporated 2024
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-06-25 Adresseendring registrert 2026-06-25.

METI TRANSPORT AS is registered as a limited company in Drammen, Buskerud with organisation number 934377389. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Transport av gods, samt alt som står i forbindelse med dette, herunder også deltagelse i andre selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 163,000 in revenue and NOK 17,000 in operating profit.

Key figures · 2024

Revenue
NOK 163,000
Operating profit
NOK 17,000
Equity
NOK 39,000
Est. value
NOK 73,000

Financial health · 2024

Liquidity
1.10
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.7%
Weak
Equity as a share of total capital

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

Who owns METI TRANSPORT AS?

MUHAMET DERVISHAJ
METI TRANSPORT AS
NOK 163,000 rev. · NOK 17,000 profit

METI TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about METI TRANSPORT AS

Who owns METI TRANSPORT AS?

MUHAMET DERVISHAJ is the largest registered owner, with 100.0%.

What is the revenue of METI TRANSPORT AS?

METI TRANSPORT AS had revenue of NOK 163,000 in 2024.

Who is the general manager of METI TRANSPORT AS?

Mari Ann Ho is registered as general manager of METI TRANSPORT AS.

Where is METI TRANSPORT AS based?

METI TRANSPORT AS has its business address in Drammen.

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.