biztrac. BETA
COMPANY REGISTER PROFILE
818124732 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
On-demand passenger transport service activities by vehicle with driver

TRONDHEIM TAXIDRIFT AS

Org. no. 818124732 Limited company (AS) Oslo Incorporated 2016 Active
Revenue 2025 NOK 371,000
Operating profit NOK −55,000
Equity NOK 5.3m
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−55k kr).

TRONDHEIM TAXIDRIFT AS is registered as a limited company in Oslo, Oslo with organisation number 818124732. The business is classified under on-demand passenger transport service activities by vehicle with driver (NACE 49.330). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Taxi-virksomhet og det som naturlig hører med.”. The most recent filed accounts, for the 2025 financial year, show NOK 371,000 in revenue and NOK −55,000 in operating profit.

Key figures · 2025

Revenue
NOK 371,000
▼ −29 %
Operating profit
NOK −55,000
▲ +69 %
Equity
NOK 5.3m
▲ +4 %
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
4.58
Very good
Current assets ÷ current liabilities
Profitability
3.2%
Weak
Return on total assets
Solidity
79.4%
Very good
Equity as a share of total capital

Who owns TRONDHEIM TAXIDRIFT AS?

TRONDHEIM TAXIDRIFT AS
NOK 371,000 rev. · NOK −55,000 profit

TRONDHEIM TAXIDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TRONDHEIM TAXIDRIFT AS

Who owns TRONDHEIM TAXIDRIFT AS?

Zulaikha Sajid Qayyum is the largest registered owner, with 100.0%.

What is the revenue of TRONDHEIM TAXIDRIFT AS?

TRONDHEIM TAXIDRIFT AS had revenue of NOK 371,000 in 2025.

Where is TRONDHEIM TAXIDRIFT AS based?

TRONDHEIM TAXIDRIFT 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 03.10.2026.

Report a problem

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