FlowsBook a callSign inCreate free accountSign up
Population and demographics

Petrol station catchment population: residents around a forecourt, against passing roads

Petrol station catchment population counts the people living near a forecourt. Why it matters less than for a shop, how to read it beside road data, and what data shows.

Part of the guide Location intelligence automation

By the xMap team · · 5 min read

Petrol station catchment population is the number of people living within a short drive of a forecourt, and for most fuel sites it is the smaller half of the story. A station sells to two crowds: residents who fill up near home and buy milk at the shop counter, and drivers passing on the road outside who never live nearby at all. Counting residents tells you how strong the first crowd is; reading the road tells you about the second. A good site decision weighs both.

This article is for fuel retailers, dealers running a single forecourt, convenience operators who share the site, and planners adding chargers. It sets out when residents matter more and when the road matters more, how to count each with location data, an invented example of a town-edge site against a highway site, the traps, and a flow that profiles every forecourt in a network.

Two kinds of trade at one pump

  • Neighbourhood trade. People who live within a few minutes fill up on their way to work or school and use the shop as a corner store. This trade is steady, comes back every week and grows with the number of homes around the site.
  • Passing trade. Drivers on a main road or highway stop because the station is on their way. This trade depends on how busy and how easy the road is, not on who lives nearby.

A station inside a residential district leans on the first. A station on an intercity road between towns leans on the second, and may have almost no residents around it at all. Most sites sit somewhere between, which is why both measures belong in one view.

Counting the residents

The Travel area block draws the area within a few minutes' drive of the forecourt along the roads, and the Demographics block counts the residents inside it from xMap's population grid: the total, women and men, nine age groups and people per square kilometre. For a fuel site, the total and the density matter most: a large, dense residential pool means steady weekday fills and shop baskets.

Five minutes by car is a sensible core for neighbourhood trade; most people do not drive far out of their way for fuel. Keep the same time when you compare sites.

Reading the passing road

This is where honesty about the data matters, because road figures differ by country.

  • Live movement, anywhere. Traffic Flow gives the current speed, the free-flow speed and a jam factor from 0 to 10 for the roads around each place. It shows whether the road outside moves freely or crawls at the hours you check. It does not count cars.
  • Car counts, in the United Arab Emirates only. For roads in the UAE, Regional data has road traffic history: cars counted on the nearest roads hour by hour since 2021, with cars per day and the busiest hour. No other country has car counts in xMap Flows today.
  • The rivals on the road. Nearby places counts the gas stations around a site, with their brands and whether they belong to chains.

An invented example: town edge or highway

Everything in this example is made up. A fuel retailer in Ontario, Canada, compares two sites near Toronto. It counts residents within a 5-minute drive of each, reads Traffic Flow on the road outside at 08:00 on a weekday, and counts gas stations within 2 km.

Made-up siteResidents within 5 min by carJam factor at 08:00Gas stations within 2 km
Edge of a suburban town21,0004.53
On a highway between towns1,8001.21

Invented figures to explain the reading; not data about Toronto or Ontario.

The town-edge site has more than ten times the residents, three rivals and a busy road at rush hour, so its trade will be mostly local: fills on the way to work and a full shop. The highway site has hardly any residents and free-flowing traffic, so its trade will be passing drivers. Neither number alone picks a winner; together they tell the retailer what kind of station each site should be, and how big its shop should be.

Traps to avoid

  • Judging a highway site by its residents. A low count there is normal and not a warning sign.
  • Reading a jam factor as volume. A jammed road can be busy, or simply narrow. The jam factor measures how slowly traffic moves, not how many cars pass.
  • Checking the road once. Live speeds change by the hour. A flow that reads Traffic Flow at the same time each weekday gives a fairer picture than one look.
  • Forgetting what changes next. Count the EV chargers around a site too, since forecourts are adding them. The EV charging block lists public charging stations nearby.

An AI employee that profiles every forecourt

  1. Schedule: every weekday at 08:00, so the road reading is taken at the same hour.
  2. My data: your stations and candidate plots, with positions.
  3. Demographics: residents within 3 km of each, as a quick stand-in for a short drive.
  4. Traffic Flow: the speed, the free-flow speed and the jam factor on the roads outside.
  5. Nearby places: each site with a count of the gas stations within 2 km.
  6. Sort and limit, then the Google Sheets app: one row per site per day.

Over a few weeks the sheet builds a picture of each site: how many people live around it, how its road behaves at 08:00 day after day, and how many rivals share it. The template New fuel stations in my region, by brand watches for new competitors, and Fast charger sites where drivers already stop looks at where charging fits. The full method is in the AI employee for site selection.

Questions

Does a petrol station need many residents nearby?

It depends on the site. A station in a residential area relies on them; a highway station lives mainly on passing drivers and can do well with very few residents.

Can xMap Flows count the cars passing a site?

Only for roads in the United Arab Emirates, through Regional data's road traffic history. Elsewhere, Traffic Flow gives live speeds and a jam factor, not car counts.

What distance should the resident count use?

A few minutes' drive is a sensible core for neighbourhood fuel trade. A 5-minute drive area or a radius of about 3 km keeps sites comparable.

Is there population data for the UK and US?

No. The population grid covers about 100 countries, including Canada, France, India and Australia, but not the United Kingdom or the United States.

Templates that do this

Read next

More on population and demographics · Every article · Templates

Put it to work

An AI employee in xMap Flows does this on live data, on its own timetable. Start from a template or describe it in plain words.