Rawalpindi
Operationally tied to Islamabad. The city's role is inseparable from twin-city commuting and should expand alongside capital-region demand.
After the first launch wave, humsafr expands into cities where rider demand, route repetition, and verified driver supply are strong enough to support reliable pooled commuting.
These cities are already part of humsafr's growth path. They follow the first three launch markets because rollout stays focused on route quality, reliable supply, and repeat commuter demand.
Operationally tied to Islamabad. The city's role is inseparable from twin-city commuting and should expand alongside capital-region demand.
Industrial and education-linked movement makes Faisalabad a strong candidate once corridor supply and rider demand are ready.
A city where trust, route clarity, and safer defaults can matter a lot once commute density and route supply align.
Repeat professional travel and clearer corridor geography make Multan a viable next-wave expansion target.
Important both as its own commuter market and as a wider south-bound extension adjacent to Karachi's network logic.
Airport, manufacturing, and business travel corridors make Sialkot a strong fit for verified recurring pooling.
Dense urban movement and proximity to other Punjab hubs make it a logical route-based expansion candidate.
Smaller than the flagship cities, but still meaningful where regional commuter patterns repeat enough to justify trusted pooled travel.
If your route is not listed yet, that does not mean it is ignored. It usually means humsafr needs clearer supply and demand signals before opening it properly.
The right launch order protects product quality. A city should only go live when route density, driver supply, and rider trust signals are strong enough to make recurring pools actually work.
The clearest signal is real intent. Riders and drivers joining from the same corridors show where the strongest next launch demand already exists.