Current League Standings | P | GD | PTS | |
8 | Vaasan Palloseura | 9 | 3 | 10 |
9 | SJK | 10 | -8 | 10 |
10 | Lahti | 10 | -7 | 9 |
Current League Standings | P | GD | PTS | |
10 | Lahti | 10 | -7 | 9 |
11 | IFK Mariehamn | 9 | -7 | 7 |
12 | HIFK Fotboll | 9 | -9 | 3 |
Our analysis of all available data, including recent performances and player stats up until an hour before kickoff, suggested the most likely outcome of this match was a SJK win with a probability of 44.19%. A win for IFK Mariehamn had a probability of 29.91% and a draw had a probability of 25.9%.
The most likely scoreline for a SJK win was 1-0 with a probability of 10.65%. The next most likely scorelines for that outcome were 2-1 (9.02%) and 2-0 (7.8%). The likeliest IFK Mariehamn win was 0-1 (8.42%), while for a drawn scoreline it was 1-1 (12.32%). The actual scoreline of 1-0 was predicted with a 10.7% likelihood. Our data analysis correctly predicted a 1-0 win for SJK in this match.
Result | ||
SJK | Draw | IFK Mariehamn |
44.19% ( 0.59) | 25.91% ( 0.18) | 29.91% ( -0.77) |
Both teams to score 52.68% ( -0.95) |
Goals |
Over 2.5 | Under 2.5 |
48.66% ( -1.06) | 51.34% ( 1.05) |
Over 3.5 | Under 3.5 |
26.84% ( -0.93) | 73.17% ( 0.93) |
SJK Goals |
Over 0.5 | Under 0.5 |
76.86% ( -0.17) | 23.14% ( 0.17) |
Over 1.5 | Under 1.5 |
42.99% ( -0.26) | 57.01% ( 0.25) |
IFK Mariehamn Goals |
Over 0.5 | Under 0.5 |
68.54% ( -1.08) | 31.46% ( 1.08) |
Over 1.5 | Under 1.5 |
32.16% ( -1.27) | 67.84% ( 1.27) |
Score Analysis |
SJK | Draw | IFK Mariehamn |
1-0 @ 10.65% ( 0.39) 2-1 @ 9.02% ( 0.02) 2-0 @ 7.8% ( 0.25) 3-1 @ 4.4% ( -0.01) 3-0 @ 3.8% ( 0.1) 3-2 @ 2.54% ( -0.08) 4-1 @ 1.61% ( -0.01) 4-0 @ 1.39% ( 0.03) 4-2 @ 0.93% ( -0.03) Other @ 2.04% Total : 44.18% | 1-1 @ 12.32% ( 0.1) 0-0 @ 7.28% ( 0.3) 2-2 @ 5.21% ( -0.14) 3-3 @ 0.98% ( -0.06) Other @ 0.11% Total : 25.91% | 0-1 @ 8.42% ( 0.11) 1-2 @ 7.13% ( -0.16) 0-2 @ 4.87% ( -0.08) 1-3 @ 2.75% ( -0.15) 2-3 @ 2.01% ( -0.12) 0-3 @ 1.88% ( -0.09) Other @ 2.86% Total : 29.91% |
ISOCountry Code:
Matched Country Groups: