Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|
| Date | Match | Score | Res |
|---|---|---|---|
| 13.08.2026 | Shelbourne - Ajax | 2 - 2 | D |
| 09.08.2026 | Shelbourne - St Patrick's Athl. | 1 - 2 | L |
| 06.08.2026 | Ajax - Shelbourne | 3 - 1 | L |
| 02.08.2026 | Waterford - Shelbourne | 1 - 0 | L |
| 30.07.2026 | Kalju Nomme - Shelbourne | 2 - 1 | L |
| Date | Match | Score | Res |
|---|---|---|---|
| 13.08.2026 | Shelbourne - Ajax | 2 - 2 | D |
| 09.08.2026 | PEC Zwolle - Ajax | 0 - 2 | W |
| 06.08.2026 | Ajax - Shelbourne | 3 - 1 | W |
| 02.08.2026 | FC Volendam - Ajax | 1 - 3 | W |
| 30.07.2026 | Ajax - Vojvodina | 4 - 1 | W |
The upcoming match between Shelbourne and Ajax is scheduled for 13.08.2026 18:45 in UEFA Europa Conference 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.
Shelbourne recorded 2 wins, 3 draws and 5 losses across the last 10 completed matches. The newest-to-oldest result sequence is LLLLWDDWDL. The averages are 1.50 goals scored and 1.90 goals conceded per match. Both teams scored in 80% of those matches, while 80% finished with over 2.5 goals. Ajax recorded 8 wins, 1 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWWWWWDWL. The averages are 2.20 goals scored and 0.90 goals conceded per match. Both teams scored in 70% of those matches, while 60% finished with over 2.5 goals.
The highest stored values are: Both teams to score — 90%; Over 1.5 goals — 90%; Over 0.5 first-half goals — 80%; Over 2.5 goals — 80%; Over 1.5 first-half goals — 60%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Ajax to win with 79% confidence. The stored fair probabilities for home, draw and away are 7.71%, 13.22% and 79.07%. The model momentum difference is 71.36 points in favour of Ajax. The input data quality score is 96/100. The stored price for the selected market is 1.17 with Bet365. The stored estimated EV is -7.48%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
The normalized movement for the Asian pair Shelbourne 0 / Ajax 0 supports Ajax by an average 1.24 percentage points across 1 bookmakers (1xBet) with up to 2 stored observations. This is a market signal, not a result guarantee.
The match between Shelbourne and Ajax ended 2-2. The game produced 4 goals in total. The first half contained 3 goals. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.
Before kickoff, the stored trend indicated BTTS at 90%. The actual outcome was BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 90%. 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 80%. The actual outcome was Over 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 3.5 at 60%. The actual outcome was Over 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 Over 1.5 HT at 60%. The actual outcome was Over 1.5 HT. The stored trend was confirmed by the result.
The Asian-handicap signal locked before kickoff supported Ajax at 0. The stored market movement was 1.24 percentage points across 1 bookmaker. At the final score of 2-2, the line settled as a push. The result is neutral and is counted as neither confirmed nor unconfirmed.
Of 7 verifiable pre-match indicators, 6 aligned with the final result and 0 were not confirmed, while 1 settled neutrally. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.