BIZTRAC BETA
Non-scheduled passenger transport by road

TURBUSS NORWEY TRANSPORT AS

Org. no. 920870422 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 5.4m
Operating profit NOK 241,000
Equity NOK 752,000
Incorporated 2018
Employees 12
Share capital NOK 30,000

TURBUSS NORWEY TRANSPORT AS is registered as a limited company in Oslo, Oslo with organisation number 920870422. The business is classified under non-scheduled passenger transport by road (NACE 49.320). The company was incorporated in 2018 and has 12 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Persontransport og godstransport på vei med buss og bil.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.4m in revenue and NOK 241,000 in operating profit.

Key figures · 2024

Revenue
NOK 5.4m
Operating profit
NOK 241,000
Equity
NOK 752,000
Est. value
NOK 1.2m

Financial health · 2025

Liquidity
1.79
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
34.9%
Good
Equity as a share of total capital

Who owns TURBUSS NORWEY TRANSPORT AS?

MAHAMED ALI AWIL
TURBUSS NORWEY TRANSPORT AS
NOK 5.4m rev. · NOK 241,000 profit

TURBUSS NORWEY TRANSPORT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TURBUSS NORWEY TRANSPORT AS

Who owns TURBUSS NORWEY TRANSPORT AS?

MAHAMED ALI AWIL is the largest registered owner, with 100.0%.

What is the revenue of TURBUSS NORWEY TRANSPORT AS?

TURBUSS NORWEY TRANSPORT AS had revenue of NOK 5.4m in 2024.

Who is the general manager of TURBUSS NORWEY TRANSPORT AS?

Mahamed Ali Awil is registered as general manager of TURBUSS NORWEY TRANSPORT AS.

Where is TURBUSS NORWEY TRANSPORT AS based?

TURBUSS NORWEY 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.