Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|
| Date | Match | Score | Res |
|---|---|---|---|
| 12.09.2026 | FC Cincinnati - Charlotte | 3 - 3 | D |
| 09.09.2026 | Philadelphia Union - FC Cincinnati | 5 - 0 | L |
| 05.09.2026 | FC Cincinnati - DC United | - | |
| 30.08.2026 | Nashville SC - FC Cincinnati | 4 - 0 | L |
| 22.08.2026 | FC Cincinnati - Seattle Sounders | 1 - 1 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 12.09.2026 | Atlante FC - Pachuca | 0 - 3 | W |
| 05.09.2026 | FC Juarez - Pachuca | 0 - 2 | W |
| 29.08.2026 | Pachuca - Guadalajara Chivas | 1 - 1 | D |
| 23.08.2026 | Atletico San Luis - Pachuca | 1 - 1 | D |
| 18.08.2026 | Pachuca - Puebla | 2 - 3 | L |
The upcoming match between FC Cincinnati and Pachuca is scheduled for 04.08.2026 23:45 in Leagues 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.
FC Cincinnati recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWWWDLDWW. The averages are 3.10 goals scored and 2.20 goals conceded per match. Both teams scored in 90% of those matches, while 90% finished with over 2.5 goals. Pachuca recorded 5 wins, 0 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLWLWWWLLW. The averages are 1.20 goals scored and 1 goals conceded per match. Both teams scored in 30% of those matches, while 40% finished with over 2.5 goals.
The highest stored values are: Over 0.5 first-half goals — 80%; Over 1.5 goals — 80%; Over 2.5 goals — 80%; Both teams to score — 70%; Over 1.5 first-half goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair FC Cincinnati -1 / Pachuca +1 supports FC Cincinnati by an average 1.60 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 3 stored observations. This is a market signal, not a result guarantee.
3 active football Premium signals are stored for this fixture. Both Teams Score — Yes (odds 1.36). Odd/Even — Odd (odds 2). At least one goal in the match (quota 19, score 82/100, 81.93% group success rate across 1245 observations).
The match between FC Cincinnati and Pachuca ended 3-1. The game produced 4 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.
Before kickoff, the stored trend indicated BTTS at 70%. 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 2.5 at 80%. The actual outcome was Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 80%. 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.
The Asian-handicap signal locked before kickoff supported FC Cincinnati at -1. The stored market movement was 1.6 percentage points across 2 bookmakers. At the final score of 3-1, the line settled as a full win. The Asian-handicap signal was confirmed.
The stored Premium market was BTTS Yes at odds of 1.36. The actual market outcome was BTTS Yes. The Premium signal was confirmed. The stored Premium market was Odd at odds of 2. The actual market outcome was Even. The Premium signal was not confirmed. The stored Premium market was At least one FT goal with quota 19. The actual market outcome was At least one FT goal. The Premium signal was confirmed.
Of 9 verifiable pre-match indicators, 8 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.