Match context

The upcoming match between Tampa Bay Rowdies and Louisville City is scheduled for 02.08.2026 00:00 in USL Championship. The analysis uses only stored statistics, form, head-to-head records, trend percentages and active Premium market signals. It does not guarantee a particular result.

Standings and season form
Tampa Bay Rowdies are in position 1 with 35 points after 17 matches. The season record is 10 wins, 5 draws and 2 losses. The goals record is 28 scored and 15 conceded. The stored form sequence is WDLWL. Louisville City are in position 4 with 24 points after 17 matches. The season record is 8 wins, 3 draws and 6 losses. The goals record is 28 scored and 26 conceded. The stored form sequence is LWDWD.

Recent results

Tampa Bay Rowdies recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWLWLDWWW. The averages are 1.80 goals scored and 1 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals. Louisville City recorded 5 wins, 3 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWLWWDDWDL. The averages are 1.40 goals scored and 1.10 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Tampa Bay Rowdies recorded 5 wins, there were 0 draws, and Louisville City recorded 5 wins. The average total was 2.70 goals per match. Both teams scored in 60% of those matches, while 60% finished with over 2.5 goals.

Trend indicators

The highest stored values are: Over 1.5 goals — 80%; Over 0.5 first-half goals — 70%; Both teams to score — 60%; Over 1.5 first-half goals — 60%; Over 2.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.

Asian handicap market movement

The normalized movement for the Asian pair Tampa Bay Rowdies -1.25 / Louisville City +1.25 supports Louisville City by an average 1.13 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 3 stored observations. This is a market signal, not a result guarantee.

What happened in the match

The match between Tampa Bay Rowdies and Louisville City ended 5-4. The game produced 9 goals in total. The first half contained 3 goals. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.

Comparison with the head-to-head history

The previous 10 head-to-head meetings averaged 2.7 goals, while this match produced 9. The final scoring profile differed by more than one goal from that average. Across the previous 10 head-to-head meetings, the leading historical direction was BTTS at 60%. The actual outcome for this indicator was BTTS. The final result aligned with that historical profile. Across the previous 10 head-to-head meetings, the leading historical direction was Over 2.5 at 60%. The actual outcome for this indicator was Over 2.5. The final result aligned with that historical profile.

Which pre-match trends were confirmed and which were not

Before kickoff, the stored trend indicated BTTS at 60%. The actual outcome was BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 80%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 70%. The actual outcome was Over 0.5 HT. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 HT at 60%. The actual outcome was Over 1.5 HT. The stored trend was confirmed by the result.

Asian handicap review

The Asian-handicap signal locked before kickoff supported Louisville City at +1.25. The stored market movement was 1.13 percentage points across 2 bookmakers. At the final score of 5-4, the line settled as a half win. The Asian-handicap signal was confirmed.

Summary

Of 8 verifiable pre-match indicators, 7 aligned with the final result and 1 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.