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 |
|---|---|---|---|
| 08.08.2026 | Tigres UANL - Minnesota United FC | 0 - 0 | D |
| 05.08.2026 | Minnesota United FC - FC Juarez | 1 - 2 | L |
| 02.08.2026 | Minnesota United FC - San Diego | 1 - 1 | D |
| 26.07.2026 | Minnesota United FC - Liberia | - | |
| 26.07.2026 | Minnesota United FC - Vancouver Whitecaps | 0 - 0 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 09.08.2026 | Real Salt Lake - Atlante FC | 4 - 0 | L |
| 05.08.2026 | Vancouver Whitecaps - Atlante FC | 0 - 1 | W |
| 02.08.2026 | Cruz Azul - Atlante FC | 2 - 3 | W |
| 25.07.2026 | Atlante FC - Club America | 1 - 1 | D |
| 17.07.2026 | Necaxa - Atlante FC | 2 - 1 | L |
The upcoming match between Minnesota United FC and Atlante FC is scheduled for 12.08.2026 00:30 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.
Minnesota United FC recorded 1 wins, 5 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLDDLDLLDW. The averages are 1 goals scored and 1.30 goals conceded per match. Both teams scored in 70% of those matches, while 50% finished with over 2.5 goals. Atlante FC recorded 3 wins, 3 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWWDLDDLLW. The averages are 1.20 goals scored and 1.70 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals.
The highest stored values are: Both teams to score — 80%; Over 1.5 goals — 80%; Under 3.5 goals — 80%; Over 0.5 first-half goals — 70%; Over 2.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Minnesota United FC -1.5 / Atlante FC +1.5 supports Minnesota United FC by an average 4.11 percentage points across 3 bookmakers (Bet365, 1xBet, Unibet) 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. Goals Over/Under — Over 1.5 (odds 1.20, score 77/100, 76.74% bucket win rate across 374 observations). At least one goal in the match (quota 15, score 81/100, 80.58% group success rate across 2482 observations).
The match between Minnesota United FC and Atlante FC ended 3-1. The game produced 4 goals in total. The first half contained 1 goal. 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 80%. 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 Under 3.5 at 80%. The actual outcome was Over 3.5. The stored trend was not 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 Under 1.5 HT at 90%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
The Asian-handicap signal locked before kickoff supported Minnesota United FC at -1.5. The stored market movement was 4.11 percentage points across 3 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 Over 1.5 FT at odds of 1.2. The actual market outcome was Over 1.5 FT. The Premium signal was confirmed. The stored Premium market was At least one FT goal with quota 15. The actual market outcome was At least one FT goal. The Premium signal was confirmed.
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.