Adam Doud/
Follow : Add us as a preferred source on Google.
Last week, while my beloved Cubbies were fighting for their playoff lives, I decided to see how speeds were doing on the three biggest carriers in the US. Since my hometown of Chicago was one of the first test beds for 5G, I've been maintaining an interest in it throughout my career.
You see, back when 5G was still in its infancy, we were sold two big promises about 5G -- speed and capacity. For speed, the biggest example we were given was "You can download an entire movie while you sit on the tarmac waiting to take off! Well, concerns surrounding 5G and airport safety quickly quashed those dreams.
Also: The best 5G phones in 2025: Where does the iPhone 17 rank?
The other promise was capacity. The promise was "you can go to a concert and still stream to your friends back home" and yadda yadda. So far, in my experience, that has very much not been the case. Any time I find myself in an amusement park or a ballgame, my phone becomes a nice camera, as long as I don't try to send photos to anyone. It's been a while since I've run into that situation, so I wanted to take the temperature these days.
When the Cubs advanced to the Wild Card playoffs, I saw an opportunity. Cubs games are typically well-represented, but considering the last time they played in front of a home crowd in the playoffs was back in 2017, I wanted to see how these networks handled me hanging around with 41,000 of my closest friends. Packing three identical Pixel 10 Pros , I headed down for some fun at the old ballpark - from the outside because getting tickets was impossible.
RECOMMENDS Google Pixel 10 Pro The latest Android handset features an updated Tensor G5 processor capable of running Google's new Gemini AI features. View at Store.google
The game plan
Since traffic around Wrigley Field (and anywhere within a three-mile radius) is perilous at the best of times, I headed over to Wrigley Field from 10 miles away (hi, mom) on my Engwe LE 20 electric bike -- side note: I ride this bike more than my car during the summer months.
Also: Your iPhone wants to track every place you visit - here's how to stop it
Fortunately (or unfortunately), I got a bit of a late start, so when the first pitch arrived at 2:08, I found myself about 4.8 miles away. That's actually OK, because I wanted to get a baseline for the networks before I moved within range of the park.
Once I was at the park, I was surprised at the lack of foot traffic outside the stadium. Granted, this was a day game, so there was less socializing outside the park. Beyond foot traffic, the biggest obstacles I anticipated that might impact connectivity were the stadium itself and all the people inside it trying to livestream or share videos of their views from the seats.
So at the corner of Lawrence and Pulaski, I ran my first tests.
Location 1: Lawrence and Pulaski
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 75.1 (Mbps) | 356 | 126 | 837 | 81.6 | 371 |
San Diego got off to a hot start with a Jackson Merrill sacrifice fly in the first inning to drive in Fernando Tatis Jr. The Cubs could not retaliate against Dylan Cease, so I was still 2.3 miles from Wrigley Field at the corner of Lincoln and Wilson when the second inning started.
Location 2: Lincoln and Wilson
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 42.2 (Mbps) | 835 | 28.5 | 528 | 20.4 | 439 |
By then, Andrew Kittredge had left the game, his role of "opener" finished, and Japanese star pitcher Shota Iminaga had entered as the actual starter for the game. For the record, I don't like openers, but I'm also not a Major League manager, so I don't get a vote. Nothing happened in the second inning, but by the beginning of the third inning, I'd arrived at the front gate of Wrigley Field for my first tests on site, and holy Toledo!
Location 3: Front gate
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 6.91 (Mbps) | 35.5 | 63.4 | 2666 | 18 | 1299 |
Those are no misplaced decimals -- those are four-digit download speeds from both Verizon and AT&T. I'll spare you the rest of the baseball recaps for here on out, but from here I moved to the right field gate.
Location 4: Right-field gate
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&TDown |
| 0 (Mbps) | 0 | 31.7 | 70.3 | 9.29 | 8.55 |
At this gate, T-Mobile refused to run a speed test at all, failing to even connect to the server. That's not great, but it would have a chance at redemption later in the game. Still, you can see the crowd may have been beginning to take a toll. On to the left field gate!
Location 5: Left-field gate
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 50.6 (Mbps) | 8.43 | 14.7 | 46.2 | 48.5 | 93.5 |
Fortunately. At the left field gate, there was a TV on in a bar that I could see from where I was standing. Also, this is where I ran my first download test. Using the same three phones, I downloaded the same 2GB file from my personal Google Drive. It was a 4K video file from a recent video project I shot. Here are the times, formatted in minutes and seconds.
| T-Mobile | Verizon | AT&T |
| 3:55 | 4:34 | 1:15 |
From here, I decided I wanted to get one more baseline, so for the fifth inning, I headed over to the lakefront, which is just about a mile away from the park.
Also: My phone struggled to get signal: These 5 quick fixes instantly improved its reception
Being separated from the crowd, the networks behaved once again, even if the Padres did not -- they scored another two runs.
Location 6: Lakefront
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 41.6 (Mbps) | 479 | 28.5 | 476 | 48.8 | 89.7 |
Once again, I headed back to the ballpark to see what the crowd had to say about those numbers. They did not agree. As I stood by the entrance to the bleachers, with the borderline creepy tribute to Harry Carey, I took another reading at the top of the 6th inning.
Location 7: Bleachers
Adam Doud/
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 0 (Mbps) | 0 | 27.9 | 163 | 6.03 | 26.8 |
Once again, T-Mobile was not participating, so I decided to head back to the right field entrance to see if it was just a Sheffield Avenue thing. It was not.
Location 8: Sheffield Avenue
| T-Mobile Up | T-Mobile Down | Verizon Up | Verizon Down | AT&T Up | AT&T Down |
| 13.7 (Mbps) | 88.9 | 17.6 | 196 | 0.45 | 4.81 |
Here lies our first mystery -- well, second mystery, actually. The first mystery is how Eddie Vedder (yes, Pearl Jam Eddie Vedder) talked his way into singing "Take Me Out to the Ballgame" two days in a row. The second mystery is how T-Mobile decided not to play at all on my first visit to this spot, literally 30 minutes ago, and now it's beating the pants off of its two competitors.
Also: How to clear your Android phone cache (and why it makes such a big difference)
Anyway, for my last test, I headed to Gallagher Way, which is a sort of entertainment spot for Cubs ticket holders outside of the park. Gallagher Way is also a popular spot for non-ticket holders due to the giant Jumbotron that broadcasts the games. That's where I stayed for the last test, which took two innings for a particular reason I'll get to in a moment. Here are the speed test results:
