BIZTRAC BETA
Central agencies for goods and transportation procurement

OSLOBY TAXI AS

Org. no. 918044825 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Equity NOK −19,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

OSLOBY TAXI AS is registered as a limited company in Oslo, Oslo with organisation number 918044825. The business is classified under central agencies for goods and transportation procurement (NACE 52.211). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300000 shares. The company's stated purpose is: “Drive drosjesentraler, herunder formidle transportoppdrag, markedsføre taxitjenester, administrere kredittkjøring, kurse/utdanne sjåfører og taxieiere. Selskapet kan inngå kontrakter med transportkjøpere og utøvere. I tillegg skal selskapet drive drosjevirksomhet selv under egen løyve eller ved å administrere andre løyver.”.

Key figures · 2024

Equity
NOK −19,000

Financial health · 2024

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-26.5%
Weak
Equity as a share of total capital

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

Who owns OSLOBY TAXI AS?

Mubin Hussain Kapur
OSLOBY TAXI AS

OSLOBY TAXI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OSLOBY TAXI AS own?

OSLOBY TAXI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about OSLOBY TAXI AS

Who owns OSLOBY TAXI AS?

Mubin Hussain Kapur is the largest registered owner, with 100.0%.

Who is the general manager of OSLOBY TAXI AS?

Mubin Hussain Kapur is registered as general manager of OSLOBY TAXI AS.

Where is OSLOBY TAXI AS based?

OSLOBY TAXI 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.