Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 08.10.2022 | Kokand-1912 - Lokomotiv | 0 : 0 |
| 11.05.2022 | Lokomotiv - Kokand-1912 | 1 : 2 |
| 23.10.2021 | Kokand-1912 - Lokomotiv | 2 : 1 |
| 20.06.2021 | Lokomotiv - Kokand-1912 | 0 : 1 |
| 25.11.2020 | Kokand-1912 - Lokomotiv | 0 : 1 |
| 21.08.2020 | Lokomotiv - Kokand-1912 | 1 : 2 |
| 20.09.2019 | Kokand-1912 - Lokomotiv | 1 : 1 |
| 02.05.2019 | Lokomotiv - Kokand-1912 | 2 : 2 |
| 09.07.2018 | Kokand-1912 - Lokomotiv | 1 : 2 |
| 07.04.2018 | Lokomotiv - Kokand-1912 | 1 : 1 |
| Date | Match | Score | Res |
|---|---|---|---|
| 08.08.2026 | Nasaf - Kokand-1912 | 0 - 0 | D |
| 03.08.2026 | Kokand-1912 - Surkhon | 0 - 1 | L |
| 29.07.2026 | Dinamo Samarqand - Kokand-1912 | 3 - 2 | L |
| 22.07.2026 | Kokand-1912 - Olmaliq | 1 - 4 | L |
| 17.07.2026 | Mash'al - Kokand-1912 | 1 - 0 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 07.08.2026 | Lokomotiv - Dinamo Samarqand | 2 - 1 | W |
| 01.08.2026 | Buxoro - Lokomotiv | 2 - 1 | L |
| 27.07.2026 | Lokomotiv - Sogdiana | 3 - 1 | W |
| 22.07.2026 | Lokomotiv - Andijan | 3 - 3 | D |
| 17.07.2026 | Pakhtakor - Lokomotiv | 1 - 1 | D |
The upcoming match between Kokand-1912 and Lokomotiv is scheduled for 15.08.2026 14:00 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
Kokand-1912 are in position 15 with 12 points after 15 matches. The season record is 2 wins, 5 draws and 8 losses. The goals record is 13 scored and 24 conceded. The stored form sequence is DLLLL. Lokomotiv are in position 6 with 25 points after 16 matches. The season record is 7 wins, 4 draws and 5 losses. The goals record is 24 scored and 22 conceded. The stored form sequence is WLWDD.
Kokand-1912 recorded 1 wins, 3 draws and 6 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLLLLWLLDD. The averages are 0.70 goals scored and 1.70 goals conceded per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals. Lokomotiv recorded 5 wins, 2 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLWDDWLWLW. The averages are 1.70 goals scored and 1.50 goals conceded per match. Both teams scored in 80% of those matches, while 70% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Kokand-1912 recorded 4 wins, there were 4 draws, and Lokomotiv recorded 2 wins. The average total was 2.20 goals per match. Both teams scored in 70% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Both teams to score — 70%; Over 1.5 goals — 70%; Over 2.5 goals — 60%; Under 3.5 goals — 60%; Over 0.5 first-half goals — 50%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Kokand-1912 -1.5 / Lokomotiv +1.5 supports Lokomotiv by an average 1.09 percentage points across 1 bookmakers (1xBet) with up to 4 stored observations. This is a market signal, not a result guarantee.
2 active football Premium signals are stored for this fixture. Both Teams Score — Yes (odds 1.78). Odd/Even — Odd (odds 2).
The discipline profile for Lokomotiv away from home is based on 3 matches. The team averages 2.00 yellow cards, 0.33 red cards and 2.33 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 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 5 of 16 completed matches (31.3% coverage).
The match between Kokand-1912 and Lokomotiv ended 2-1. 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.
The historical profile from 10 head-to-head meetings averaged 2.2 goals, while this match produced 3. The result remained within one goal of the historical average. Across the previous 10 head-to-head meetings, the leading historical direction was BTTS at 70%. The actual outcome for this indicator was BTTS. The final result aligned with that historical profile.
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 70%. 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 60%. The actual outcome was Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 60%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 70%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
Before kickoff, the discipline profile for Lokomotiv away from home was based on 3 matches, with averages of 2 yellow cards, 0.33 red cards and 2.33 total cards per match. In this game, Lokomotiv received 0 yellow cards and 0 red cards, 0 in total. That was 2.33 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%.
The Asian-handicap signal locked before kickoff supported Lokomotiv at +1.5. The stored market movement was 1.09 percentage points across 1 bookmaker. At the final score of 2-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.78. 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 Odd. The Premium signal was confirmed.
Of 10 verifiable pre-match indicators, 9 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.