Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 01.05.2026 | Diyala - Al Talaba | 0 : 1 |
| 27.01.2026 | Al Talaba - Diyala | 1 : 1 |
| 14.02.2025 | Al Talaba - Diyala | 0 : 0 |
| 12.12.2024 | Diyala - Al Talaba | 0 : 1 |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Diyala - Al Talaba | 2 - 1 | W |
| 01.06.2026 | Diyala - Duhok | 1 - 0 | W |
| 27.05.2026 | Al-Karma - Diyala | 1 - 0 | L |
| 19.05.2026 | Diyala - Baghdad | 1 - 4 | L |
| 15.05.2026 | Diyala - Al Shorta | 0 - 2 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 15.08.2026 | Diyala - Al Talaba | 2 - 1 | L |
| 01.06.2026 | Al Talaba - Al Karkh | 1 - 1 | D |
| 28.05.2026 | Al Minaa Basra - Al Talaba | 1 - 1 | D |
| 19.05.2026 | Al Talaba - Al-Karma | 1 - 1 | D |
| 15.05.2026 | Al Quwa Al Jawiya - Al Talaba | 2 - 1 | L |
The upcoming match between Diyala and Al Talaba is scheduled for 15.08.2026 15:30 in Iraqi 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.
Diyala recorded 4 wins, 1 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLLLWDLWLW. The averages are 0.90 goals scored and 1.20 goals conceded per match. Both teams scored in 30% of those matches, while 30% finished with over 2.5 goals. Al Talaba recorded 3 wins, 5 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is DDDLDLWWDW. The averages are 1.50 goals scored and 1.30 goals conceded per match. Both teams scored in 80% of those matches, while 50% finished with over 2.5 goals.
Across the last 4 head-to-head matches, Diyala recorded 0 wins, there were 2 draws, and Al Talaba recorded 2 wins. The average total was 1 goals per match. Both teams scored in 25% of those matches, while 0% finished with over 2.5 goals.
The highest stored values are: Over 0.5 first-half goals — 80%; Over 1.5 goals — 80%; Under 3.5 goals — 80%; Both teams to score — 70%; Under 2.5 goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
The match between Diyala and Al Talaba ended 2-1. The game produced 3 goals in total. The first half contained 1 goal. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
The previous 4 head-to-head meetings averaged 1 goals, while this match produced 3. The final scoring profile differed by more than one goal from that average. Across the previous 4 head-to-head meetings, the leading historical direction was No BTTS at 75%. The actual outcome for this indicator was BTTS. The final result did not align with that historical profile. Across the previous 4 head-to-head meetings, the leading historical direction was Under 2.5 at 100%. The actual outcome for this indicator was Over 2.5. The final result did not align 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 80%. 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 80%. 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 80%. 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.
Of 9 verifiable pre-match indicators, 5 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.