HELLO CYCLING - シェアサイクル

Name: HELLO CYCLING - シェアサイクル
Rating: 3 (19243 reviews)
Author: OPENSTREET CO.,LTD.

By: OPENSTREET CO.,LTD.

Anytime, anywhere you feel free to use HELLO CYCLING is a share cycle that can be used throughout the country.

Features & Capabilities

HELLO CYCLING offers shared bicycles at over 13,000 locations nationwide with electric‑assist bikes for daily life and sightseeing. The app enables easy reservations from your current location and lets you choose a return station; rentals start from 30 minutes.

Sign up in minutes (email or Yahoo! JAPAN ID) and pay with PayPay, Credit Card, Carrier Billing, or Yahoo! Wallet. Note prices differ by region and always review the Terms of Service before use.

User Growth & Download Statistics

App Navigation & Mapping

By:

OPENSTREET CO.,LTD.

Downloads:

1,495,180 6.04K

Rating:

3.00

(19,243) 76 new ratings

Version:

3.20.4 Last updated: 2026-05-28

Version code:

205

Creation date:

2020-05-21

Publisher country:

Permissions:

android.permission.ACCESS_COARSE_LOCATION Very high risk
android.permission.ACCESS_FINE_LOCATION Very high risk
android.permission.CAMERA Very high risk
android.permission.BLUETOOTH Moderate risk
android.permission.BLUETOOTH_ADMIN Moderate risk
android.permission.BLUETOOTH_CONNECT Moderate risk
android.permission.BLUETOOTH_SCAN Moderate risk
com.google.android.gms.permission.AD_ID Moderate risk
android.permission.ACCESS_ADSERVICES_AD_ID Low risk
android.permission.ACCESS_ADSERVICES_ATTRIBUTION Low risk

Size:

42.24MB

Email:

cu*****@hellocycling.jp

URLs:

Website ,Privacy policy

Full description:

Source:

Google Play Store

Data ingested on:

2026-06-04

Compare stats and ranking:

Ranking

# 52,934 ▼ 46

For Developers

Monetize with App Pass Boost with Extension Booster

Contact the developer

Chrome-Stats does not own this Android app. Please use these information below to contact the Android app developer.

Developed by:

OPENSTREET CO.,LTD.

Google Play Store

https://play.google.com/store/apps/details?id=jp.hellocycling.hellocycling

Email:

cu*****@hellocycling.jp

Website:

https://www.hellocycling.jp

Publisher Change History

2025-01-21: he*****@gmail.com to cu*****@hellocycling.jp

Upgrade to see full email

User Reviews

Top concerns center on onboarding: the app supports only a few country codes and SMS verification often fails, making sign-up difficult for travelers. Users report Canada listed but signup still fails; other countries like Australia or Philippines are not accessible in the app. Reliability issues persist: docking racks are scarce, parking spots can be unavailable or far away, and some bikes are unusable or have low battery. UX problems also surface: cluttered screens, language issues, and occasional compatibility changes after updates. A minority state the app works or is 'very good' when registration succeeds.

Pros

Some users report the app works and rate it as 'very good'.
The core bike rental concept is present and usable when users can complete onboarding.
Canada is listed as a supported country code in the app, indicating some level of international country coverage.

Cons

Registration is blocked for many travelers because only a limited set of country codes is supported and requires an active phone number.
SMS verification often fails or is not sent, preventing account creation.
Some reviews show inconsistent country support (e.g., Canada listed as supported but signup still fails; Australia/Philippines not accessible in the app).
Bike availability and parking/return issues are common: racks are scarce, parking spots can be unavailable or far away, and some bikes are unusable or have low battery.
UI/UX and compatibility problems: cluttered screens, language issues, and occasional compatibility changes after updates.

Recent reviews

Very easy to use, also English available

Ev*****, 2026-05-21

It's literally impossible to use the app, because the Account creation screen is not resized to fit on my smartphone screen, so there is no confirmation button after typing in your phone number. How is it possible that this is not caught in testing?