Red Bull Arena in Harrison, New Jersey, hosts a pivotal 2026 MLS regular‑season clash at 7:30 PM EDT on ESPN. Chicago Fire FC sit third with a +11 goal difference and 35 points, fueled by Hugo Cuypers’ 13 goals and Philip Zinckernagel’s 8 assists, while Red Bull New York are eighth at –12 GD and 25 points, relying on Julian Hall’s nine strikes and Emil Forsberg’s 7 assists. Both sides have generated plenty of chances—Chicago with 19 team assists, New York with 21—setting up a contest where midfield control and transition speed will likely decide the tempo. Chicago’s high‑press shape aims to force errors and feed Cuypers in the final third, exploiting the space behind New York’s more conservative back line. New York will look to dictate possession through Forsberg’s incisive passing and Hall’s poise inside the box, but their leaky defense (42 goals conceded) suggests vulnerability to quick counters. With the over/under set at 3.5, expect a tightly contested, momentum‑driven affair where a single decisive chance could swing the night.
SOCCER Matchup Preview
Chicago Fire FC at Red Bull New York: 2026 MLS, Regular Season Preview
2026 MLS, Regular Season
Sat, August 22nd at 7:30 PM EDT
ESPN
Red Bull Arena
Harrison, New Jersey, USA
Fixture
Chicago Fire FC at Red Bull New York
Kickoff
Sat, August 22nd at 7:30 PM EDT
Competition
2026 MLS, Regular Season
Venue
Red Bull Arena
Location
Harrison, New Jersey, USA
Coverage
ESPN
What To Watch
- The market angle right now is CHI +135.
- One storyline hanging over the match: Miami's Lionel Messi fined by MLS for slapping opponent.
Sofia Touchline's Pick
Chicago Fire FC
Sofia Touchline is backing Chicago Fire FC over Red Bull New York in this matchup.
Prop Hub
Make your pick and talk it out here
This article is now the home for the linked prop, your pick action, and the same prop discussion thread.
Matchup
Chicago Fire FC vs Red Bull New York
Start
2026-08-22 19:30:00
Status
Finished
Discussion
Prop chat
Load the thread when you want it. That keeps us from initializing Disqus just because someone opened the article.
No thread is loaded yet.
