Sports bar foot traffic on match nights: reading the street before kick-off
How to read presence around a bar on game evenings: which weeks had a big match, how the evening share moves, and how your street compares with rival bars nearby.
Part of the guide Location intelligence automation
Sports bar foot traffic on a match night shows up as a heavier evening on the street around the bar, not as a count of who walked through your door. To see it, measure the area around the bar a week at a time, note which weeks had a big evening fixture, and compare those weeks with quiet ones: the evening share of the day, the busiest hour and the busiest weekday move when a match pulls people out. Do the same for the rival bars nearby, and you learn whether match crowds come to your street or pass it for another.
This is for owners and managers of pubs and bars that show live sport on screens, often far from any stadium, and for the drinks brands and leagues that pick which bars to back. It covers what the figures can and cannot say about a game evening, a made-up example in Madrid, the traps, and a weekly AI employee that keeps the record for you.
What the figures say about a game evening
The Mobility Footfall block measures presence in the area around a place: people-hours, scaled from a panel of devices to the whole population, so someone who stays two hours on the block counts twice. That suits a bar better than a door count would, because a match crowd lingers. It also means the number belongs to the street, not the bar: the kebab shop, the bus stop and the flats upstairs are in it too.
Each run gives an average day over the window you choose, the busiest hour, how the day splits into morning, midday, evening and late night, the busiest and quietest weekday, and the last seven days against the seven before. There is no figure for one named evening. A single Thursday fixture is one day in seven, so it nudges a weekly window rather than jumping out of it.
Finding the match weeks in the record
Because one evening is diluted, the trick is to keep many short readings and line them up with the fixture list you already know. Seven-day windows, taken every week, give you a row per week. Next to each row, write whether that week had a big evening match, a cup run, a derby or nothing at all.
Three fields carry most of the signal:
- The evening and late-night shares. On a week with a late kick-off, the share of the day after 6 pm tends to rise even if the daily total barely moves.
- The busiest hour. If it slides from the after-work hour to later in the evening on fixture weeks, that is the crowd waiting for kick-off and staying for the result.
- The busiest weekday. A street that is usually busiest on Saturday but tops out on a Wednesday during a midweek tournament is reacting to the screens.
Run the same measure with Weekdays only and Weekends only as separate columns. Midweek matches hide inside an all-days average because the weekend is so much larger.
A made-up example: a bar in Madrid
Everything in this example is invented to show the method. A bar in a Madrid neighbourhood about twenty minutes from the nearest stadium shows every big European night. The owner wants to know whether to hire a second bartender on fixture evenings, and whether a rival bar three streets away is taking the crowd.
Over a season of weekly rows, the evening share around the bar sits near a third of the day in quiet weeks and climbs noticeably in weeks with a late midweek match. The busiest hour moves from early evening to around kick-off. Around the rival, the same weeks show almost no change: the crowd stays near a square where both a metro exit and a large screen sit, and the rival's corner is off that path.
The owner hires for fixture evenings only, moves the staff rota for the quiet midweek nights, and asks a drinks brand for screen support using the season's record rather than a guess. Nothing here proves how many people came inside; it shows when the street around the bar fills, which is the part the owner could not see before.
Comparing your street with other bars
Measure rivals the same way or the comparison is worthless. Use the same radius, the same window and the same day type for every bar. The Nearby places block can find the bars and pubs within a short walk, and Mobility Footfall then measures each one in the same run, so the rows line up. Up to about 200 metres the measure uses the bar's own block of the map; wider, it adds every block whose middle falls inside the circle, which pulls in the next street.
For the bigger picture of what this kind of data is good for, the guide to location intelligence automation covers presence, population and places side by side.
Traps to avoid
- Reading people-hours as customers. A busy street outside a bar with a shut door is still a busy street.
- Judging a single week. One wet fixture night or a bank holiday can swing a row; look for the pattern across several match weeks.
- Forgetting the delay. A row taken this Monday describes a week that ended about ten days ago, so date your fixture column to match.
- Mixing day types. Comparing your weekend-only figure with a rival's all-days figure says nothing.
- Expecting figures everywhere. Coverage is wide but not complete, and a place with no data says so rather than inventing a number.
A weekly AI employee for the record
You do not need to remember to pull the numbers. An AI employee can keep the season's log and send it to you each Monday.
- Start with a Schedule block set to every Monday morning.
- Add your bar and the rivals you care about, or let Nearby places find the bars within a short walk of yours.
- Add Mobility Footfall with a small radius, a 7-day window and the busy hours, busiest days and trend figures.
- Use Sort and limit to put the highest evening share first.
- Send the rows to a sheet or by Email, and add your fixture column by hand each week.
After a few months, the sheet answers the questions that matter for the bar: which nights are worth extra staff, which fixtures move the street, and whether your corner or someone else's catches the crowd.
Questions
Can footfall tell me how many people watched the match in my bar?
No. It measures presence in the area around the bar in people-hours, so it describes the street, not the room. Pair it with your till data for what happened inside.
Why can I not see last night's match?
Each day's figures arrive about ten days later, and the measure gives an average day over a window rather than one evening. Use it to plan fixtures to come, not to react tonight.
Which window works best for match weeks?
Seven days, taken every week, so each row covers one week you can mark as a fixture week or not. Longer windows blur single matches into the average.
Does it work for bars far from the stadium?
Yes, and that is often where it is most useful: the screen crowd gathers in neighbourhoods, and the evening share around those streets moves on big nights.