biztrac. BETA
COMPANY REGISTER PROFILE
997929160 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other postal and courier activities

HUSSNAIN TRANSPORT AS

Org. no. 997929160 Limited company (AS) Lillestrøm Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 28.5m
Operating profit NOK 3.0m
Equity NOK 4.7m
Incorporated 2012
Employees 28
Share capital NOK 30,000

HUSSNAIN TRANSPORT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 997929160. The business is classified under other postal and courier activities (NACE 53.200). The company was incorporated in 2012 and has 28 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Bud/varelevering og alt som hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 28.5m in revenue and NOK 3.0m in operating profit.

Key figures · 2025

Revenue
NOK 28.5m
▼ −2 %
Operating profit
NOK 3.0m
▲ +84 %
Equity
NOK 4.7m
▲ +63 %
Est. value
NOK 9.0m

Financial health · 2025

Liquidity
1.88
Good
Current assets ÷ current liabilities
Profitability
16.1%
Very good
Return on total assets
Solidity
26.3%
Good
Equity as a share of total capital

Who owns HUSSNAIN TRANSPORT AS?

HUSSNAIN TRANSPORT AS
NOK 28.5m rev. · NOK 3.0m profit

HUSSNAIN TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUSSNAIN TRANSPORT AS

Who owns HUSSNAIN TRANSPORT AS?

Salabat Ali is the largest registered owner, with 100.0%.

What is the revenue of HUSSNAIN TRANSPORT AS?

HUSSNAIN TRANSPORT AS had revenue of NOK 28.5m in 2025.

Who is the general manager of HUSSNAIN TRANSPORT AS?

Salabat Ali is registered as general manager of HUSSNAIN TRANSPORT AS.

Where is HUSSNAIN TRANSPORT AS based?

HUSSNAIN TRANSPORT AS has its business address in Skedsmokorset.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.