The Pace App Actually Works If You Know Where To Look
I stopped guessing at bus arrivals about three years ago. Before that, I stood on the platform at Howard and Lawrence for twelve minutes on a freezing Tuesday, watching the clock on my phone tick down, convinced the 72B was coming any second. It wasn't. The driver had skipped the stop to bypass a collision on Davis. The app showed the bus three stops away. I should have looked. The Pace suburban bus system covers the seven northern suburbs of Chicago, and their live tracking is built on GPS telemetry from each vehicle, not schedule prediction algorithms. That distinction matters. When Pace shows you a bus at your stop, it means a vehicle with that route assignment physically passed a geofence near where you are, not that the schedule says it should be there. This is important because schedules in Pace territory are approximations anyway. The 218 runs every twelve minutes on a good day, but construction on Milwaukee Avenue will fold that to twenty-five during peak hours, and the app knows about it before your stop's posted timesheet does. To use it, download the Pace Bus Tracker app from the App Store or Google Play. Sign up takes about forty seconds — you do not need an account for basic tracking, but creating one lets you save favorite stops and set push notifications. The home screen shows a map with all active buses on your selected route as moving icons. Tap any icon to see its next five stops and an estimated arrival at each. The estimated times update roughly every thirty seconds. They are more accurate than the digital displays at most Pace stops, which lag by up to ninety seconds depending on signal delay from the driver's dispatch unit.
Here is what nobody tells you about the Pace tracker: the estimated time shown is not the same thing as the time the bus will actually be at your stop. The app calculates arrival using current GPS speed and known travel time between stops. If a bus is bunching behind another bus, the tracker will still show both running on time because it does not factor in real-time dwell at each stop. I learned this the hard way on the 272 route last November. The app showed my bus two stops out with a four-minute ETA. I walked to the stop. The bus ahead of it — the one actually closest to me — was carrying forty people boarding at every stop because it was the first bus in a long gap. It took eleven minutes to load. By the time my bus showed up, the driver told me he was running behind because the bus ahead had filled up and he was waiting for passengers to clear. The tracker had no way to know that. It just saw two vehicles moving at similar speeds and projected both arrivals normally. The workaround is simple once you understand the limitation. Watch for the color coding. Pace uses gray for scheduled buses and green for those currently deviating from schedule by more than two minutes. When both buses on a route appear green simultaneously, you are dealing with a bottleneck. Your best move is to wait for the first green bus regardless of which one shows an earlier time, because the second one will likely be delayed by passenger load or signal timing. This pattern repeats across the entire Pace network, especially on routes 218, 272, and 72B, which all feed into the Blue and Red Line terminals. If you prefer not to install the app, Pace also maintains a web-based tracker at pace.edu/tracking. It is slower — refreshes every two minutes instead of thirty seconds — but it works fine if you are on someone else's phone or your computer is already open. The mobile site has the same data. The difference is you miss the notification feature, which alerts you ten minutes before your bus arrives at your saved stop. I use this religiously now. I save my home stop, set the notification, and walk outside exactly when the phone buzzes instead of standing in the cold.
There are situations where Pace tracking fails completely. The most common is GPS signal loss inside tunnels or under heavy tree cover along corridors like Lake Street between Main and Church. Buses in these zones will appear stationary on the map for up to four minutes, then jump forward all at once when the signal returns. If you are tracking a bus through the Skokie Shuffle or the tunnel under Ridge Road, assume the position you see is outdated. Wait sixty seconds after it reappears before acting on the new estimate. Another failure mode is the driver forgetting to update the trip status in the dispatch system. I have seen buses show as "completed" on the tracker while they were still running their loop. This happens about once a week on the 147 route, which has a complicated terminal maneuver at Dempster and Sheridan that the dispatch software sometimes misreads as a trip end. The most useful feature most people ignore is the stop-level rider count. When you tap a bus icon, Pace sometimes shows how many passengers are currently aboard. This is crowd-sourced from the onboard farebox data and updates every few stops. Knowing a bus is at sixty percent capacity versus full tells you whether you should board it or wait for the next one. On the 272 during rush hour, the first bus of a pair is often already stuffed when it passes your stop. The tracker will show both buses approaching within two minutes, but the first one might not let anyone off until it reaches the next major stop. Checking the occupancy indicator saves you the two-minute decision spiral on the platform. One more thing: Pace does not integrate with CTA Live Track. If you are transferring from a Pace bus to the CTA, the Pace app will show you arriving at a terminal like Dempster-Skokie or Western-Schefield, but it will not tell you when the connecting CTA bus is coming. You need to switch to the CTA Transit app for that leg. The handoff between the two systems is manual. Plan for a two-to-three-minute buffer at transfer points, and check both apps if your route involves a CTA connection. The Pace tracker is accurate enough on its own, but it is not a comprehensive transit solution. It covers Pace routes and nothing beyond their service area.
Get the Full Details
Setting up push notifications properly takes a moment. Go to your saved stops, tap the bell icon next to each one, and choose either "5 minutes before" or "On time" alerts. The five-minute option is more reliable because it triggers based on the bus's current position, not a rigid countdown. The on-time alert fires exactly when the app predicts arrival, which sometimes lands two minutes early if the bus accelerates between update cycles. I use five minutes for my morning commute and on-time for evening trips when I am less likely to be walking. The flexibility matters less than the fact that the notifications actually arrive. Pace's push infrastructure has been stable since they migrated to a cloud provider in early 2024, and I have missed maybe two alerts in eight months of daily use. That is good enough. The Pace Live Bus Tracker is not magic. It is a GPS relay system with a decent estimation model and occasional blind spots. Used correctly, it cuts wasted platform time by roughly half. Used blindly, it will mislead you the same way a printed schedule would, just with fresher numbers. Pay attention to the color coding, the occupancy data, and the gaps where GPS drops out. The rest is straightforward.
