Error message

  • Deprecated function: Return type of Aws\HandlerList::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 32 of /var/www/html/vendor/aws/aws-sdk-php/src/HandlerList.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Api\AbstractModel::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Api/AbstractModel.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of & Aws\Endpoint\Partition::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Return type of Aws\Endpoint\Partition::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 13 of /var/www/html/vendor/aws/aws-sdk-php/src/Endpoint/Partition.php).
  • Deprecated function: Aws\Credentials\Credentials implements the Serializable interface, which is deprecated. Implement __serialize() and __unserialize() instead (or in addition, if support for old PHP versions is necessary) in include() (line 8 of /var/www/html/vendor/aws/aws-sdk-php/src/Credentials/Credentials.php).
  • Deprecated function: Return type of Aws\Command::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of & Aws\Command::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Command::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 7 of /var/www/html/vendor/aws/aws-sdk-php/src/Command.php).
  • Deprecated function: Return type of Aws\Result::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of & Aws\Result::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::getIterator() should either be compatible with IteratorAggregate::getIterator(): Traversable, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Deprecated function: Return type of Aws\Result::count() should either be compatible with Countable::count(): int, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in include() (line 9 of /var/www/html/vendor/aws/aws-sdk-php/src/Result.php).
  • Warning: Undefined array key "nid" in views_handler_field_term_node_tid->pre_render() (line 98 of /var/www/html/docroot/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).
  • Warning: Undefined array key "nid" in views_handler_field_term_node_tid->pre_render() (line 98 of /var/www/html/docroot/sites/all/modules/views/modules/taxonomy/views_handler_field_term_node_tid.inc).
×

Entertainment

We put together the best U.S. road trip routes for the 2026 World Cup

The 2026 World Cup — the first World Cup to ever be joint-hosted by three countries (USA–Mexico–Canada), will see the U.S. host 60 games in 11 stadiums across the country between June 8 and July 3 of that summer. It’s going to be nuts.

This will be the second time the United States hosts the World Cup competition.

Although there are about as many venues in U.S. tourist attracting cities for the competition than you can ask for, there’s been a growing dissatisfaction with one particular thing about the choosing of the venues in such a large country.

The key difference between 2022 and 2026 World Cup

In the 2022 World Cup, Qatar built eight stadiums in the city of Doha to create a jam-packed soccer experience for fans who — if they wished to do so — could attend multiple games on the same day. The farthest distance between stadiums was around 40 miles. 

Dissimilar to Qatar, the stadiums for the upcoming World Cup were not built solely for the tournament, and considering the U.S. is one of the largest countries in the world, the distance between venues will make a tremendous jump from those in 2022. For the 2026 World Cup, the closest distance between stadiums will be 95 miles. Get ready to travel, soccer fans.

View this post on Instagram

A post shared by The18 (@the18soccer)

Long distance travel, more accommodations and larger expenditures — some of soccer fans' concerns for the upcoming tournament.

Yet, even when these might be seen as a hassle for most, we at The18 would like to believe that this is a perfect opportunity to take advantage of the disadvantages that this World Cup will bring as opposed to 2022.

In light of the distances between venues and games for the tournament, we offer fans who plan on attending the World Cup in 2026 a fun and unique way to get the most out of the return of the tournament to the U.S. since 1994: road-tripping!

The locations of the 11 venues in the U.S. will allow for the planning of three different road trip routes that will take you to three or more matches in multiple states and with numerous tourist locations in between and along the trip.

You can choose to rent and pack the classic American road tripping RV with your family and friends, or solo-adventure into what will be the biggest World Cup (48 teams) in history. You will be able to enjoy all the World Cup all while having the opportunity to visit America’s most widely-renowned cities and tourist attractions.

Now, without further ado, here are the best U.S. cities to start a road trip at for the 2026 World Cup.

Best U.S road trip routes/cities for the 2026 World Cup

Los Angeles–San Francisco–Seattle

Perhaps the most beautiful and best sight-seeing, but longer route on this list.

View this post on Instagram

A post shared by The18 (@the18soccer)

This road trip route will have you start out attending a game at either Los Angeles’ SoFi Stadium (rumored to host the opening match) or Seattle’s Lumen Field, two of the most beautiful sports venues in the country.

Embed from Getty Images

The total travel distance between each end point will be 1,185 miles (about a 17-hour drive) with San Francisco’s Levi’s Stadium as your second stadium destination of the trip.

Embed from Getty Images

The distance between Seattle and San Francisco will be 835 miles (about a 13-hour drive), whereas the distance between Los Angeles and San Francisco will be 350 miles (about a 6-hour drive).

What’s there to visit?

Driving through basically the entire west coast will have you travel along the beautiful greens of the upper west coast between Oregon and Washington, the Golden Gate Bridge in San Francisco and with a vast pool of tourist attraction locations in the city of Los Angeles.

Embed from Getty Images

Philadelphia–New York–Boston

The closest distance between stadiums in the World Cup. 

View this post on Instagram

A post shared by The18 (@the18soccer)

This road trip will see you start out attending a game at either Philadelphia’s Lincoln Financial Field or Boston’s Gillete Stadium, two stadiums built in the 21st century.

Embed from Getty Images

The total travel distance of the trip and between each end point will be 305 miles (about a 5-hour drive) with New York’s MetLife Stadium as your second stadium destination of the trip. 

Embed from Getty Images

The distance between Boston and New York will be 210 miles (about a 4-hour drive), whereas the distance between Philadelphia and New York will be 95 miles (about a 1-hour-and-30-min drive).

What’s there to visit?

This road trip route takes you to cities that have an abundance of tourist attractions. Traveling through the upper northeast will give you the opportunity to visit the Boston National Historical Park, bounce around New York through the Statue of Liberty, Times Square and Empire State Building and learn a bit more about the history of the country in Philadelphia with the Franklin Institute, the Liberty Bell or the Independence National Historical Park.

Embed from Getty Images

Houston–Dallas–Kansas City

Not the best of the three road trip routes, but it’ll work.

View this post on Instagram

A post shared by The18 (@the18soccer)

This road trip will see you start out attending a game at either Houston’s NRG Stadium or Kansas City’s Arrowhead stadium (one of the oldest venues of the World Cup).

Embed from Getty Images

The total travel distance of the trip and between each end point will be 760 miles (about a 12-hour drive) with Dallas’ AT&T Stadium as your second stadium destination of the trip.

Embed from Getty Images

The distance between Houston and Dallas will be 240 miles (about a 4-hour drive), whereas the distance between Kansas City and Dallas will be 520 miles (about an 8-hour drive).

What’s there to visit?

Traveling through the spine Texas and Missouri will offer more than just soccer games. You will be able to visit the Houston Zoo, Space Center and Museum of Natural Science, Dallas’ World Aquarium and Arboretum and Botanical Garden, and Kansas City’s National WWI Museum and Memorial or The Nelson-Atkins Museum of Art.

Videos you might like