Rural and low density
Two buses a day, and one of them runs empty
Villages ten kilometres apart, an ageing population and a timetable that can't serve either affordably. This is what flexible transport does in places like yours — and where it already runs.
Does this describe your network?
Four things transport planners say out loud
Low-density areas fail a timetable for structural reasons, not for lack of effort: the distances are long, the demand is thin and it is spread across the day. Each symptom below leads to the scenario that answers it, and the service model it belongs to.
- 01“The 17:40 carries two people”The route runs because somebody might travel, and mostly nobody does.See the scenario ↓
- 02“Most of our riders are over 70”Appointments, market days and no smartphone — a service designed around an app misses them.See the scenario ↓
- 03“Only one road ever fills a bus”A corridor that works, ringed by stops that see one passenger a day.See the scenario ↓
- 04“Two vehicles is the whole fleet”No budget for more, and a region that looks far too big for what you have.See the scenario ↓
Scenario 01 — Village to town, every day
One zone instead of a route long enough to reach everyone
The daily rural trip — village to the market town, the bank, the supermarket, the connection onward — is what the timetable serves worst: too many settlements to include, too few passengers at each. A single service zone covers all of them, and the vehicle forms a different route each hour around whoever has actually asked to travel.
- Service zones and virtual stops
- Dynamic routing and pooling
- Fixed-line protection
- Runs on your existing fleet
In a low-density area the heaviest users are often the oldest: hospital and clinic appointments, the weekly market, visits into town. That demand is regular and predictable, but it does not arrive through an app. Phone booking, operator-created trips and strict arrival windows are the difference between a service they use and one they hear about.
- Booking by phone, web or app
- Booking on a rider’s behalf
- Strict arrival windows
- Bulk repeat rides
Scenario 03 — A corridor worth keeping, edges worth flexing
Keep the bus line that works, open its edges on request
Many rural networks have one corridor that genuinely fills — the school and commuter run into town — surrounded by stops that see a passenger a day. A dynamic bus line keeps the corridor fixed and published, and turns the rarely used branches into stops the vehicle only visits when someone has requested them.
- Fixed spine, published timetable
- On-request edge stops
- Route recalculated per trip
- Same vehicles, fewer empty kilometres
Scenario 04 — A two-vehicle fleet and a very large map
Find out what your fleet can cover before you buy anything
The hardest question in a rural business case is how much service two or three vehicles can actually deliver. A free simulation answers it on your own travel data: it designs the zone, sizes the fleet, sets the operating hours and simulates the result — so the proposal that goes to the council or the funder arrives costed, not hoped.
- Demand analysis and simulation
- Zone and stop design
- Fleet sizing
- Cost per trip reporting
Typical service shape
What a rural service usually looks like
Ranges from Shotl's rural deployments, so you can hold them against your own network before any conversation. Your simulation will produce the real numbers.
- 2–7 vehicles
- Minibuses or vans from your existing fleet, sized by simulation rather than by guess.
- 100–250 km²
- One service zone covering the villages a fixed route could never all include.
- 07:00–19:00
- Weekday coverage in most services, extended to evenings or weekends where demand exists.
- 100–600 stops
- Virtual stops placed in software — no shelters built, no timetable reprinted.
- 3 booking channels
- App, web portal and telephone, plus operators booking on a rider’s behalf.
- Cost per pax ↓
- Falling cost per passenger is the usual outcome, because kilometres follow requests.
FAQ
Rural and low-density mobility questions, answered
Our villages only have a few hundred people. Is that too small?
No — small settlements are the case flexible transport is strongest in. Instead of a route long enough to include every village, one zone covers them all and the vehicle only visits the ones with a request. Stradella serves 28 villages across 234 km² with two vehicles.
Most of our riders don't use smartphones. Does that rule us out?
No. Trips can be booked by phone call to your call centre, on a web portal, or by an operator or family member on the rider's behalf. In several rural services the phone remains the main channel.
We only have two vehicles. Is that enough?
Often yes, and simulation tells you before you commit. The simulation uses your existing travel data to size the fleet against real demand and shows what a two- or three-vehicle service can cover.
Will this replace our fixed rural line?
Only where it should. The routing engine checks whether an existing line already serves a journey adequately and guides the rider to it if so. Many networks keep the corridor fixed and make the branches flexible — that is a dynamic bus line.
What about school and medical trips we already contract separately?
Both can run on the same platform: home-to-school routes with strict times, and door-to-door appointment trips with protected arrival windows, sharing vehicles with the general service where the rules allow.
How long does a rural service take to launch?
Typically a few weeks: zone and stop design, simulation, driver onboarding and rider communication — the last one matters most in villages, where word of mouth is the channel.
