BIZTRAC BETA
Wholesale of clothing and footwear

EZYRIDE AS

Org. no. 826782722 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 10,000
Operating profit NOK −19,000
Equity NOK −204,000
Incorporated 2021
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−204k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).
  • Nylig endring 2026-04-08 Adresseendring registrert 2026-04-08.

EZYRIDE AS is registered as a limited company in Oslo, Oslo with organisation number 826782722. The business is classified under wholesale of clothing and footwear (NACE 46.420). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Passasjertransport på forespørsel utført av fører med kjøretøy.”. The most recent filed accounts, for the 2024 financial year, show NOK 10,000 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 10,000
Operating profit
NOK −19,000
Equity
NOK −204,000

Financial health · 2024

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

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

Who owns EZYRIDE AS?

AON RAZA NAQVI
EZYRIDE AS
NOK 10,000 rev. · NOK −19,000 profit

EZYRIDE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about EZYRIDE AS

Who owns EZYRIDE AS?

AON RAZA NAQVI is the largest registered owner, with 100.0%.

What is the revenue of EZYRIDE AS?

EZYRIDE AS had revenue of NOK 10,000 in 2024.

Who is the general manager of EZYRIDE AS?

Ramla Imtiaz Ahmad is registered as general manager of EZYRIDE AS.

Where is EZYRIDE AS based?

EZYRIDE 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.