Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 04.04.2026 | Pakhtakor - Olmaliq | 3 : 1 |
| 05.08.2025 | Pakhtakor - Olmaliq | 1 : 2 |
| 09.04.2025 | Pakhtakor - Olmaliq | 2 : 1 |
| 16.03.2025 | Olmaliq - Pakhtakor | 2 : 0 |
| 21.11.2024 | Pakhtakor - Olmaliq | 0 : 2 |
| 21.06.2024 | Olmaliq - Pakhtakor | 4 : 2 |
| 28.09.2023 | Pakhtakor - Olmaliq | 2 : 2 |
| 22.04.2023 | Olmaliq - Pakhtakor | 1 : 2 |
| 15.09.2022 | Olmaliq - Pakhtakor | 0 : 2 |
| 02.05.2022 | Pakhtakor - Olmaliq | 0 : 0 |
| Date | Match | Score | Res |
|---|---|---|---|
| 03.09.2026 | Olmaliq - Xorazm | 1 - 0 | W |
| 25.08.2026 | Surkhon - Olmaliq | 0 - 0 | D |
| 19.08.2026 | Olmaliq - Dinamo Samarqand | 0 - 1 | L |
| 13.08.2026 | Buxoro - Olmaliq | 2 - 0 | L |
| 08.08.2026 | Bunyodkor - Olmaliq | 2 - 3 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 04.09.2026 | Pakhtakor - Andijan | 3 - 0 | W |
| 29.08.2026 | Neftchi - Pakhtakor | 1 - 0 | L |
| 25.08.2026 | Dinamo Samarqand - Pakhtakor | 1 - 1 | D |
| 21.08.2026 | Pakhtakor - Surkhon | 0 - 0 | D |
| 16.08.2026 | Nasaf - Pakhtakor | 1 - 2 | W |
The upcoming match between Olmaliq and Pakhtakor is scheduled for 09.09.2026 13:30 in Super League. 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
Olmaliq are in position 6 with 29 points after 15 matches. The season record is 7 wins, 4 draws and 4 losses. The goals record is 24 scored and 20 conceded. The stored form sequence is DLLWL. Pakhtakor are in position 2 with 40 points after 16 matches. The season record is 10 wins, 5 draws and 1 losses. The goals record is 28 scored and 16 conceded. The stored form sequence is DDWDD.
Olmaliq recorded 5 wins, 2 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDLLWLWWWD. The averages are 1.40 goals scored and 1.10 goals conceded per match. Both teams scored in 50% of those matches, while 50% finished with over 2.5 goals. Pakhtakor recorded 5 wins, 4 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLDDWWDDWW. The averages are 1.40 goals scored and 0.60 goals conceded per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Olmaliq recorded 4 wins, there were 2 draws, and Pakhtakor recorded 4 wins. The average total was 2.90 goals per match. Both teams scored in 60% of those matches, while 60% finished with over 2.5 goals.
The highest stored values are: Under 3.5 goals — 90%; Over 1.5 goals — 60%; Under 2.5 goals — 60%; Over 0.5 first-half goals — 50%; Both teams to score — 40%. They are statistical indicators and are not automatically converted into a prediction.
The discipline profile for Olmaliq at home is based on 3 matches. The team averages 1.67 yellow cards, 0.33 red cards and 2.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 66.7%, 33.3%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 33.3%. Season card data is available for 9 of 20 completed matches (45.0% coverage). The discipline profile for Pakhtakor away from home is based on 5 matches. The team averages 1.40 yellow cards, 0.20 red cards and 1.60 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 60.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 20.0%. Season card data is available for 9 of 20 completed matches (45.0% coverage).
The match between Olmaliq and Pakhtakor ended 1-3. The game produced 4 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.
The previous 10 head-to-head meetings averaged 2.9 goals, while this match produced 4. 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.
Before kickoff, the stored trend indicated No BTTS at 60%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 60%. The actual outcome was Over 1.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 60%. 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 Over 3.5. The stored trend was not 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.
Before kickoff, the discipline profile for Olmaliq at home was based on 3 matches, with averages of 1.67 yellow cards, 0.33 red cards and 2 total cards per match. In this game, Olmaliq received 1 yellow cards and 0 red cards, 1 in total. That was 1 cards below the stored average. In the pre-match sample, 3+ cards occurred in 33.3% of matches, 5+ in 0%, and a red card in 33.3%. Before kickoff, the discipline profile for Pakhtakor away from home was based on 5 matches, with averages of 1.4 yellow cards, 0.2 red cards and 1.6 total cards per match. In this game, Pakhtakor received 2 yellow cards and 0 red cards, 2 in total. That was 0.4 cards above the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 20%.
Of 8 verifiable pre-match indicators, 3 aligned with the final result and 5 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.