Baku Bus Atlas

Independent research · Baku, Azerbaijan

Baku’s bus network,
under the lens.

How routes connect. Where they overlap. Who lives near a stop. An open-data study of published routes, built to explore, question and reproduce.

Read the research paper Preprint · PDF ↗
FIG. 01 / PUBLISHED NETWORK40° N · 50° E
routes · served stopsAYNA snapshot

What the snapshot shows

Definitions & assumptions
meet the directness threshold
/
Path ≤1.4× the straight line in both directions. A geometry classification, not a service rating.
flagged detour segments
Meet the study’s distance thresholds. have a shorter graph path; road feasibility needs review.
high-overlap route pairs
≥85% of one route’s stops also served by another. Shared stops alone do not establish redundant service.
estimated population coverage
Within 400 m straight-line distance, using the 2023 population grid in the study area. Try other distances ↗

01 / Explore the evidence

One network. Nine ways to look.

Choose a layer, then select a route or search for a stop. Follow the geometry, compare shared stops, explore modelled travel times, or see where the bicycle lanes and parking points meet the buses.

02 / Test an assumption

How near is
near a stop?

Coverage depends on where you draw the line. Change the distance threshold to explore five recorded calculations from the same network and population grid, each measured two ways: in a straight line, and walking along the streets and paths in OpenStreetMap.

Distance, not walking access. The study’s measure is the straight line; the darker bars walk the same distance along mapped streets and paths, so the straight line’s error is visible. Street crossings, terrain, unmapped paths and service frequency are not evaluated. The map’s coverage layer stays at 400 m in a straight line.
Download the five results CSV ↗ Download the walking check CSV ↗

Choose a straight-line distance

Kontur Population · November 2023 · people in the study area. Values rounded to one decimal place.

03 / Check the source

The data deserves a closer look, too.

Issues detected in the captured public map API (map-api.ayna.gov.az), grouped by type. Automatic corrections are applied to this study’s working network; some unusable shapes use straight lines between stops. Select a route to inspect the evidence.

04 / From findings to questions

A checklist for further investigation.

The first ten entries of each list. Download the workbook for all flagged detours, high-overlap pairs, corridors and stop-spacing candidates. These flags need local and operational review.

05 / Inspect the detail

All routes and carriers

All routes with usable stop data in this snapshot, with the same measurements grouped by carrier. Filter or sort any column to investigate. Carrier totals describe assigned route geometry, not operating performance.

06 / Make it reproducible

How it was measured

Snapshot measurements

Lengths, shared stops and geometric thresholds describe the repaired map data.

Model estimates

Coverage uses a population grid. Travel times use assumed speeds and mostly estimated headways.

Requires validation

Changes to routes or stops need rider counts, road checks and local knowledge.

Routes, stops and route lines come from AYNA's public map API, taken on ; the data is identical, row for row, to a copy taken on . Defects in the map data were detected and repaired automatically, as listed above. Residents come from the Kontur population grid (November 2023, hexagons of about 0.74 km²) and boardings from the daily counts BakuBus publishes on opendata.az (, weekday average). Bicycle lanes and parking points are AYNA's, from its opendata.az datasets (files of 24 September and 4 May 2026, CC0).

Direct route
In both directions the path is at most 1.4 times the straight line between the end stops. Indirect: 1.4 to 2 times, very indirect: 2 to 3 times, loop: more than 3 times, or ends less than 1 km apart.
Detour
A stretch where the bus travels at least 2.5 times the straight line between two of its stops, and at least 1.5 km more (12 stops at most). The extra minutes are estimates from speeds assumed by type of service.
Shorter path
A shortest graph path between a flagged segment’s ends, using stop-to-stop links in the snapshot and short connectors between nearby stops. Shown when at least 0.5 km shorter. The modelled time difference includes assumed speeds and 20 seconds per net intermediate stop avoided; it is not a verified saving or a road-feasibility check.
Near-duplicate
At least 85% of the stops of a route with 10 or more stops are also served by one other route. Express routes are left out: skipping stops is what they are for.
Corridor
A stretch of street of at least 1 km where every link between consecutive stops carries at least 8 routes.
Stop spacing
A stop is flagged by the spacing scenario when, on every route that uses it, it lies less than 250 m along the route from a neighbouring stop and removing it leaves no gap over 700 m. Terminals and interchange hubs are kept, and stops served by fewer routes go first. This geometric rule does not establish that a stop should be removed.
Reach
The stops on the routes that stop at a given stop; with one change, also the stops of every route that stops within 300 m of those. It counts connections, not minutes.
Travel time
Estimated minutes by bus from a stop, from the paper's travel model: half a route's headway of waiting at each boarding, the ride at speeds set by type of service with 20 seconds lost at each stop, and walks of up to 300 m between stops to change buses, which are avoided as if each change cost 5 minutes. Headways are estimated for 200 of the 201 routes, so the minutes are estimates.
Carriers
The routes each carrier runs, as AYNA's map assigns them, with their figures added up. AYNA plans the routes, so the figures describe the routes, not how well a carrier runs them. Names that differ only in spelling are counted once, which gives the paper's 39 carriers.
Coverage
Estimated population within a straight-line radius of a served stop, using the November 2023 Kontur grid. Each hexagon is represented by seven equally weighted points. The study area is the served-stop bounding box plus 2 km, not Baku’s administrative boundary. The default radius is 400 m; the coverage lab uses five recorded radii from 300 m to 1 km.
Bicycles
AYNA's existing bicycle lanes and its bicycle parking points, as published on opendata.az. A stop is within 100 m of a lane in a straight line; a route runs along a lane where its path lies within 40 m of one, sampled every 20 m, so that a lane on one side of a dual carriageway counts for a bus on the other. The parking file also holds 649 points named MPS whose purpose it does not state; they are drawn small and blue. People within 400 m of a lane are counted as coverage counts them.

The study has no comprehensive observed timetables, vehicle positions or origin–destination records. The captured API omits eight routes present in the September 2026 boarding records. Two identical snapshots establish equality on those dates; they do not establish that the API was unchanged throughout the interval.

Directness and overlap alone do not measure service quality: indirect routes can serve important destinations, and shared routes can offer useful frequency or different connections. A shorter path in the graph is not a verified drivable alternative; legal turns, one-way streets, skipped stops and rider impacts need checking.

The paper also explores a redesign under a fixed modelled bus-hour budget. Its results depend on estimated headways and demand; the route paths shown here do not establish real-world time, fleet or fuel savings. The preprint reports the assumptions and sensitivity checks.