Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 30.10.2023 | Oriental - Racing Montevideo | 1 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 12.09.2026 | Oriental - Miramar | 1 - 3 | L |
| 06.09.2026 | Tacuarembo - Oriental | 0 - 1 | W |
| 03.09.2026 | Oriental - Racing Montevideo | 1 - 2 | L |
| 30.08.2026 | Oriental - Plaza Colonia | 2 - 0 | W |
| 26.08.2026 | Juventud - Oriental | 1 - 0 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 12.09.2026 | Racing Montevideo - Boston River | 3 - 2 | W |
| 09.09.2026 | Racing Montevideo - Central Espanol | 2 - 4 | L |
| 06.09.2026 | Cerro - Racing Montevideo | 1 - 0 | L |
| 03.09.2026 | Oriental - Racing Montevideo | 1 - 2 | W |
| 31.08.2026 | Racing Montevideo - Albion FC | 1 - 0 | W |
The upcoming match between Oriental and Racing Montevideo is scheduled for 03.09.2026 23:00 in Copa Uruguay. 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.
Oriental recorded 3 wins, 3 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWDLLWDLD. The averages are 1 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 20% finished with over 2.5 goals. Racing Montevideo recorded 3 wins, 6 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWDWLDDDD. The averages are 0.80 goals scored and 0.50 goals conceded per match. Both teams scored in 30% of those matches, while 10% finished with over 2.5 goals.
Across the last 1 head-to-head matches, Oriental recorded 1 wins, there were 0 draws, and Racing Montevideo recorded 0 wins. The average total was 1 goals per match. Both teams scored in 0% of those matches, while 0% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 90%; Under 2.5 goals — 80%; Over 0.5 first-half goals — 60%; Over 1.5 goals — 50%; Both teams to score — 30%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Oriental -0.25 / Racing Montevideo +0.25 supports Oriental by an average 3.71 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 14 stored observations. This is a market signal, not a result guarantee.
1 active football Premium signals are stored for this fixture. Goals Over/Under — Under 2.5 (odds 1.90).
The match between Oriental and Racing Montevideo ended 1-2. The game produced 3 goals in total. The first half contained 2 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
Before kickoff, the stored trend indicated No BTTS at 70%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 80%. The actual outcome was Over 2.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 90%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 60%. 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 80%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
The Asian-handicap signal locked before kickoff supported Racing Montevideo at +0.25. The stored market movement was 3.71 percentage points across 3 bookmakers. At the final score of 1-2, the line settled as a full win. The Asian-handicap signal was confirmed.
The stored Premium market was Under 2.5 at odds of 1.9. The actual market outcome was Over 2.5. The Premium signal was not confirmed.
Of 7 verifiable pre-match indicators, 3 aligned with the final result and 4 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.