BIZTRAC BETA
Freight transport by road

LOGISTIKK PARTNER AS

Org. no. 925741000 Limited company (AS) Lillestrøm Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 9.0m
Operating profit NOK 420,000
Equity NOK −39,000
Incorporated 2020
Employees 10
Share capital NOK 30,000

Signals

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

LOGISTIKK PARTNER AS is registered as a limited company in Lillestrøm, Akershus with organisation number 925741000. The business is classified under freight transport by road (NACE 49.410). The company was incorporated in 2020 and has 10 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Godstransport.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.0m in revenue and NOK 420,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.0m
Operating profit
NOK 420,000
Equity
NOK −39,000
Est. value
NOK 2.3m

Financial health · 2025

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

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

Who owns LOGISTIKK PARTNER AS?

ZESHAN BAHADAR
LOGISTIKK PARTNER AS
NOK 9.0m rev. · NOK 420,000 profit

LOGISTIKK PARTNER AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about LOGISTIKK PARTNER AS

Who owns LOGISTIKK PARTNER AS?

ZESHAN BAHADAR is the largest registered owner, with 12.5%.

What is the revenue of LOGISTIKK PARTNER AS?

LOGISTIKK PARTNER AS had revenue of NOK 9.0m in 2025.

Who is the general manager of LOGISTIKK PARTNER AS?

Qudrat Ullah Butt is registered as general manager of LOGISTIKK PARTNER AS.

Where is LOGISTIKK PARTNER AS based?

LOGISTIKK PARTNER AS has its business address in Sørum.

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.