Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 12.04.2024 | Opatija - Jadran LP | 0 : 0 |
| 07.10.2023 | Jadran LP - Opatija | 2 : 3 |
| 03.06.2023 | Jadran LP - Opatija | 4 : 1 |
| 25.11.2022 | Opatija - Jadran LP | 1 : 1 |
| Date | Match | Score | Res |
|---|---|---|---|
| 30.05.2026 | Jadran LP - Križevci | 1 - 0 | W |
| 23.05.2026 | Dakovo-Croatia - Jadran LP | 0 - 6 | W |
| 16.05.2026 | Lucko - Jadran LP | 2 - 3 | W |
| 09.05.2026 | Jadran LP - Varteks Varaždin | 2 - 1 | W |
| 01.05.2026 | Hrvatski Dragovoljac - Jadran LP | 0 - 5 | W |
| Date | Match | Score | Res |
|---|---|---|---|
| 18.07.2026 | Opatija - Austria Salzburg | 1 - 1 | D |
| 29.05.2026 | Opatija - Karlovac 1919 | 3 - 1 | W |
| 23.05.2026 | Dubrava Zagreb - Opatija | 3 - 2 | L |
| 15.05.2026 | Opatija - Croatia Zmijavci | 3 - 1 | W |
| 10.05.2026 | Hrvace - Opatija | 0 - 2 | W |
The upcoming match between Jadran LP and Opatija is scheduled for 22.08.2026 15:30 in First NL. 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.
Jadran LP recorded 8 wins, 2 draws and 0 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWWWDDWWW. The averages are 2.40 goals scored and 0.50 goals conceded per match. Both teams scored in 40% of those matches, while 50% finished with over 2.5 goals. Opatija recorded 4 wins, 4 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is DWLWWDWDDL. The averages are 1.50 goals scored and 0.90 goals conceded per match. Both teams scored in 60% of those matches, while 30% finished with over 2.5 goals.
Across the last 4 head-to-head matches, Jadran LP recorded 1 wins, there were 2 draws, and Opatija recorded 1 wins. The average total was 3 goals per match. Both teams scored in 75% of those matches, while 50% finished with over 2.5 goals.
The highest stored values are: Over 0.5 first-half goals — 90%; Over 1.5 goals — 80%; Over 1.5 first-half goals — 70%; Over 2.5 goals — 70%; Both teams to score — 50%. They are statistical indicators and are not automatically converted into a prediction.
The normalized movement for the Asian pair Jadran LP -1 / Opatija +1 supports Jadran LP by an average 3.96 percentage points across 2 bookmakers (Bet365, 1xBet) with up to 2 stored observations. This is a market signal, not a result guarantee.
The match between Jadran LP and Opatija ended 2-2. The game produced 4 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 historical profile from 4 head-to-head meetings averaged 3 goals, while this match produced 4. The result remained within one goal of the historical average. Across the previous 4 head-to-head meetings, the leading historical direction was BTTS at 75%. The actual outcome for this indicator was BTTS. The final result aligned with that historical profile.
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 Over 2.5 at 70%. The actual outcome was Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 90%. The actual outcome was Over 0.5 HT. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 HT at 70%. The actual outcome was Under 1.5 HT. The stored trend was not confirmed by the result.
The Asian-handicap signal locked before kickoff supported Jadran LP at -1. The stored market movement was 3.96 percentage points across 2 bookmakers. At the final score of 2-2, the line settled as a full loss. The Asian-handicap signal was not confirmed.
Of 7 verifiable pre-match indicators, 5 aligned with the final result and 2 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.