Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 16.05.2026 | Jezero - Mladost DG | 2 : 2 |
| 15.03.2026 | Mladost DG - Jezero | 3 : 1 |
| 26.11.2025 | Mladost DG - Jezero | 0 : 2 |
| 22.11.2025 | Jezero - Mladost DG | 0 : 0 |
| 17.09.2025 | Mladost DG - Jezero | 0 : 1 |
| 24.01.2025 | Mladost DG - Jezero | 0 : 0 |
| 04.05.2024 | Jezero - Mladost DG | 0 : 1 |
| 09.03.2024 | Mladost DG - Jezero | 0 : 1 |
| 04.11.2023 | Jezero - Mladost DG | 2 : 0 |
| 25.08.2023 | Mladost DG - Jezero | 1 : 2 |
| Date | Match | Score | Res |
|---|---|---|---|
| 09.08.2026 | Jezero - Mladost DG | 1 - 0 | W |
| 02.08.2026 | Jezero - Mornar | 0 - 0 | D |
| 03.06.2026 | Iskra - Jezero | 1 - 5 | W |
| 29.05.2026 | Jezero - Iskra | 3 - 0 | W |
| 24.05.2026 | Jezero - Mornar | 0 - 2 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 09.08.2026 | Jezero - Mladost DG | 1 - 0 | L |
| 02.08.2026 | Mladost DG - Otrant-Olympic | 2 - 1 | W |
| 17.07.2026 | Mladost DG - FK Vozdovac | 3 - 3 | D |
| 24.05.2026 | Arsenal Tivat - Mladost DG | 1 - 4 | W |
| 20.05.2026 | Mladost DG - Sutjeska | 0 - 1 | L |
The upcoming match between Jezero and Mladost DG is scheduled for 09.08.2026 18:00 in First League. The listed venue is Stadion pod Racinom, Plav. 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.
Jezero recorded 2 wins, 4 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is DWWLLDLLDD. The averages are 1.20 goals scored and 1.30 goals conceded per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals. Mladost DG recorded 4 wins, 2 draws and 4 losses across the last 10 completed matches. The newest-to-oldest result sequence is WDWLDWWLLL. The averages are 1.50 goals scored and 1.30 goals conceded per match. Both teams scored in 60% of those matches, while 60% finished with over 2.5 goals.
Across the last 10 head-to-head matches, Jezero recorded 5 wins, there were 3 draws, and Mladost DG recorded 2 wins. The average total was 1.80 goals per match. Both teams scored in 30% of those matches, while 30% finished with over 2.5 goals.
The highest stored values are: Over 1.5 goals — 80%; Under 3.5 goals — 70%; Over 0.5 first-half goals — 60%; Both teams to score — 50%; Over 2.5 goals — 50%. They are statistical indicators and are not automatically converted into a prediction.
The match between Jezero and Mladost DG ended 1-0. The game produced 1 goal in total. The first half contained 1 goal. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.
The historical profile from 10 head-to-head meetings averaged 1.8 goals, while this match produced 1. The result remained within one goal of the historical average. Across the previous 10 head-to-head meetings, the leading historical direction was No BTTS at 70%. The actual outcome for this indicator was No BTTS. The final result aligned with that historical profile. Across the previous 10 head-to-head meetings, the leading historical direction was Under 2.5 at 70%. The actual outcome for this indicator was Under 2.5. The final result aligned with that historical profile.
Before kickoff, the stored trend indicated Over 1.5 at 80%. 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 70%. 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 70%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.
Of 7 verifiable pre-match indicators, 6 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.