Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 30.04.2026 | Yaypan - Gazalkent | 1 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 06.09.2026 | Lochin - Gazalkent | 1 - 1 | D |
| 28.08.2026 | Gazalkent - FarDu | 0 - 1 | L |
| 21.08.2026 | Kattaqurgon - Gazalkent | 2 - 4 | W |
| 14.08.2026 | Gazalkent - Olimpik-Mobiuz | 0 - 1 | L |
| 09.08.2026 | BuxDu - Gazalkent | 1 - 3 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 06.09.2026 | Yaypan - Shortan | 1 - 4 | L |
| 25.08.2026 | Jayxun - Yaypan | 3 - 1 | L |
| 20.08.2026 | Yaypan - Pakhtakor II | 2 - 0 | W |
| 15.08.2026 | Qiziriq - Yaypan | 1 - 2 | W |
| 10.08.2026 | Metalourg - Yaypan | 1 - 1 | D |
The upcoming match between Gazalkent and Yaypan is scheduled for 11.09.2026 13:00 in Pro League A. 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
Gazalkent are in position 8 with 28 points after 13 matches. The season record is 6 wins, 3 draws and 4 losses. The goals record is 24 scored and 16 conceded. The stored form sequence is DLWLW. Yaypan are in position 10 with 21 points after 13 matches. The season record is 4 wins, 2 draws and 7 losses. The goals record is 14 scored and 23 conceded. The stored form sequence is LLWWD.
Gazalkent recorded 5 wins, 2 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is DLWLWWLWWD. The averages are 2 goals scored and 1 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals. Yaypan recorded 2 wins, 2 draws and 6 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLWWDDLLLL. The averages are 1 goals scored and 2 goals conceded per match. Both teams scored in 70% of those matches, while 60% finished with over 2.5 goals.
Across the last 1 head-to-head matches, Gazalkent recorded 1 wins, there were 0 draws, and Yaypan recorded 0 wins. The average total was 3 goals per match. Both teams scored in 100% of those matches, while 100% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 70%; Under 3.5 goals — 60%; Both teams to score — 50%; Over 0.5 first-half goals — 50%; Over 2.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.
The discipline profile for Gazalkent at home is based on 1 matches. The team averages 0.00 yellow cards, 1.00 red cards and 1.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 0.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 100.0%. Season card data is available for 3 of 18 completed matches (16.7% coverage).
The match between Gazalkent and Yaypan ended 0-0. The game produced 0 goals in total. The first half contained 0 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 Over 1.5 at 70%. The actual outcome was Under 1.5. The stored trend was not 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 60%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Before kickoff, the discipline profile for Gazalkent at home was based on 1 matches, with averages of 0 yellow cards, 1 red cards and 1 total cards per match. In this game, Gazalkent received 0 yellow cards and 1 red cards, 1 in total. The total was effectively equal to the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 100%.
Of 3 verifiable pre-match indicators, 2 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.