Hapoel Petah Tikva vs Hapoel Jerusalem Ligat Ha'al prediction & result
Final score: Hapoel Petah Tikva 1-0 Hapoel Jerusalem.
Before kick-off the model made it 37% Hapoel Petah Tikva, 37% draw, 26% Hapoel Jerusalem — fair odds of 2.70, 2.70 and 3.85.
Most likely scoreline: 1-0.
Published · updated
All Israeli Ligat Ha'al predictions →
Has the model earned this number?
Hapoel Petah Tikva at 37%: of 4,828 settled 30–40% forecasts, 33.4% came in (average 33.7%). It can be read literally. The full record.
How the model saw it, minute by minute
Rebuilt after the match from the model's pre-match expected goals, frozen in the log before kick-off, plus the score and cards as they stood at each minute — never anything later. A ball marks each of the 1 goal. The same replay scores the in-play model on the track record.
Match analysis
Match timeline
Match stats — Hapoel Petah Tikva vs Hapoel Jerusalem
Line-ups
- 1O. KatzG
- 2A. CohenD
- 12S. IsraeliD
- 5A. Moucketou-MoussoundaD
- 25O. DganiD
- 72Y. NassarD
- 8T. AltmanM
- 29B. Amian
- 26K. KimvuidiF
- 9F. RivollierF
- 16R. David
- 18A. Mashiah
- 3H. Shalom
- 66M. Meir
- 14E. Asante
- 6I. EhudM
- 28N. Cohen
- 24G. BadashF
- 77Cle
- 7S. Mazal
- 55N. ZamirG
- 26I. Cohen
- 4Y. Laish
- 3N. MalmudD
- 20O. NadirD
- 91C. TiehiM
- 70S. ZuberuM
- 25A. IdokoF
- 10V. DamascanF
- 19N. Warsana
- 22T. Haimovich
- 1B. GordinG
- 16O. AgvadishM
- 18L. O. Mizrahi
- 11Y. Distelfeld
- 5A. Farada
- 14O. Abuhav
- 7O. AlmagorF
- 33I. DappaF
- 17A. Sani
Ligat Ha'al table
| # | Team | P | W | D | L | GF | GA | GD | Pts |
|---|---|---|---|---|---|---|---|---|---|
| 12 | Hapoel Petah Tikva | 10 | 2 | 0 | 8 | 5 | 17 | -12 | 6 |
| 10 | Hapoel Jerusalem | 10 | 2 | 3 | 5 | 16 | 23 | -7 | 9 |
Where the two sides stand today, not on the day of this match. Full table
Leading scorers: Hapoel Petah Tikva and Hapoel Jerusalem
Hapoel Petah Tikva
No player in Ligat Ha'al's leading scorers — 5 league goals as a side.
Hapoel Jerusalem
GoalsAssists
- N. Vrasana50
- A. Idoko42
Top 3 by league goals this season; player availability is not in the model. How to read this.