Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 02.08.2026 | Tampa Bay Rowdies - Louisville City | 5 : 4 |
| 30.05.2026 | Louisville City - Tampa Bay Rowdies | 0 : 2 |
| 08.06.2025 | Louisville City - Tampa Bay Rowdies | 2 : 1 |
| 19.04.2025 | Tampa Bay Rowdies - Louisville City | 1 : 2 |
| 12.10.2024 | Louisville City - Tampa Bay Rowdies | 2 : 1 |
| 15.06.2024 | Tampa Bay Rowdies - Louisville City | 3 : 2 |
| 14.10.2023 | Louisville City - Tampa Bay Rowdies | 2 : 3 |
| 09.09.2023 | Tampa Bay Rowdies - Louisville City | 2 : 1 |
| 05.11.2022 | Louisville City - Tampa Bay Rowdies | 1 : 0 |
| 13.08.2022 | Louisville City - Tampa Bay Rowdies | 1 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 12.08.2026 | Tampa Bay Rowdies - Louisville City | 0 - 0 | D |
| 09.08.2026 | Orange County SC - Tampa Bay Rowdies | 0 - 3 | W |
| 02.08.2026 | Tampa Bay Rowdies - Louisville City | 5 - 4 | W |
| 25.07.2026 | Miami FC - Tampa Bay Rowdies | 2 - 3 | W |
| 18.07.2026 | Loudoun United - Tampa Bay Rowdies | 1 - 1 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 12.08.2026 | Tampa Bay Rowdies - Louisville City | 0 - 0 | D |
| 09.08.2026 | Louisville City - San Antonio | 1 - 1 | D |
| 02.08.2026 | Tampa Bay Rowdies - Louisville City | 5 - 4 | L |
| 29.07.2026 | Louisville City - Birmingham Legion | 2 - 1 | W |
| 26.07.2026 | Louisville City - Trinidad and Tobago | 1 - 0 | W |
The upcoming match between Tampa Bay Rowdies and Louisville City is scheduled for 12.08.2026 23:00 in USL League One Cup. 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 9 points after 4 matches. The season record is 4 wins, 0 draws and 0 losses. The goals record is 10 scored and 1 conceded. The stored form sequence is WWW. Louisville City are in position 1 with 6 points after 4 matches. The season record is 4 wins, 0 draws and 0 losses. The goals record is 13 scored and 4 conceded. The stored form sequence is WW.
Tampa Bay Rowdies recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWDWLWLDW. The averages are 2.10 goals scored and 1.40 goals conceded per match. Both teams scored in 50% of those matches, while 50% 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 DLWWLWWDDW. The averages are 1.80 goals scored and 1.40 goals conceded per match. Both teams scored in 60% of those matches, while 50% finished with over 2.5 goals.
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 3.50 goals per match. Both teams scored in 70% of those matches, while 70% finished with over 2.5 goals.
The highest stored values are: Over 0.5 first-half goals — 90%; Over 1.5 goals — 90%; Both teams to score — 80%; Over 1.5 first-half goals — 70%; Over 2.5 goals — 70%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Tampa Bay Rowdies 0 / Louisville City 0 supports Louisville City by an average 3.48 percentage points across 2 bookmakers (Pinnacle, 1xBet) with up to 3 stored observations. This is a market signal, not a result guarantee.
2 active football Premium signals are stored for this fixture. At least one goal in the match (quota 12.50, score 89/100, 89.29% group success rate across 56 observations). Odd/Even — Odd (odds 2.02).
The match between Tampa Bay Rowdies and Louisville City ended 0-0. The game produced 0 goals in total. The first half contained 0 goals. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.
The previous 10 head-to-head meetings averaged 3.5 goals, while this match produced 0. 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 70%. The actual outcome for this indicator was No BTTS. The final result did not align with that historical profile. Across the previous 10 head-to-head meetings, the leading historical direction was Over 2.5 at 70%. The actual outcome for this indicator was Under 2.5. The final result did not align with that historical profile.
Before kickoff, the stored trend indicated BTTS at 80%. The actual outcome was No BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 90%. The actual outcome was Under 1.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 2.5 at 70%. The actual outcome was Under 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 3.5 at 60%. The actual outcome was Under 3.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 90%. The actual outcome was Under 0.5 HT. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 HT at 70%. The actual outcome was Under 1.5 HT. The stored trend was not confirmed by the result.
The Asian-handicap signal locked before kickoff supported Louisville City at 0. The stored market movement was 3.48 percentage points across 2 bookmakers. At the final score of 0-0, the line settled as a push. The result is neutral and is counted as neither confirmed nor unconfirmed.
The stored Premium market was At least one FT goal with quota 12.5. The actual market outcome was No FT goals. The Premium signal was not confirmed. The stored Premium market was Odd at odds of 2.02. The actual market outcome was Even. The Premium signal was not confirmed.
Of 12 verifiable pre-match indicators, 0 aligned with the final result and 11 were not confirmed, while 1 settled neutrally. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.