Current League Standings | P | GD | PTS | |
14 | Tromso IL | 14 | -7 | 16 |
15 | Jerv | 16 | -23 | 11 |
16 | Kristiansund | 15 | -20 | 5 |
Current League Standings | P | GD | PTS | |
13 | FK Haugesund | 16 | -4 | 16 |
14 | Tromso IL | 14 | -7 | 16 |
15 | Jerv | 16 | -23 | 11 |
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 Tromso IL win with a probability of 39.81%. A win for Kristiansund had a probability of 35.59% and a draw had a probability of 24.6%.
The most likely scoreline for a Tromso IL win was 1-2 with a probability of 8.66%. The next most likely scorelines for that outcome were 0-1 (8.07%) and 0-2 (6.11%). The likeliest Kristiansund win was 2-1 (8.12%), while for a drawn scoreline it was 1-1 (11.44%). The actual scoreline of 1-1 was predicted with an 11.4% likelihood.
Result | ||
Kristiansund | Draw | Tromso IL |
35.59% ( -2.59) | 24.6% ( -0.25) | 39.81% ( 2.84) |
Both teams to score 59.08% ( 0.78) |
Goals |
Over 2.5 | Under 2.5 |
56.11% ( 1.07) | 43.89% ( -1.08) |
Over 3.5 | Under 3.5 |
33.72% ( 1.04) | 66.28% ( -1.04) |
Kristiansund Goals |
Over 0.5 | Under 0.5 |
75.77% ( -0.9) | 24.22% ( 0.9) |
Over 1.5 | Under 1.5 |
41.43% ( -1.29) | 58.57% ( 1.29) |
Tromso IL Goals |
Over 0.5 | Under 0.5 |
77.97% ( 1.94) | 22.03% ( -1.94) |
Over 1.5 | Under 1.5 |
44.64% ( 2.85) | 55.36% ( -2.85) |
Score Analysis |
Kristiansund | Draw | Tromso IL |
2-1 @ 8.12% ( -0.35) 1-0 @ 7.57% ( -0.57) 2-0 @ 5.36% ( -0.56) 3-1 @ 3.84% ( -0.27) 3-2 @ 2.9% ( -0.03) 3-0 @ 2.54% ( -0.34) 4-1 @ 1.36% ( -0.13) 4-2 @ 1.03% ( -0.04) Other @ 2.89% Total : 35.59% | 1-1 @ 11.44% ( -0.18) 2-2 @ 6.14% ( 0.09) 0-0 @ 5.34% ( -0.25) 3-3 @ 1.46% ( 0.07) Other @ 0.21% Total : 24.59% | 1-2 @ 8.66% ( 0.35) 0-1 @ 8.07% ( 0.09) 0-2 @ 6.11% ( 0.4) 1-3 @ 4.37% ( 0.41) 2-3 @ 3.1% ( 0.22) 0-3 @ 3.08% ( 0.36) 1-4 @ 1.65% ( 0.24) 2-4 @ 1.17% ( 0.14) 0-4 @ 1.16% ( 0.19) Other @ 2.45% Total : 39.81% |
ISOCountry Code:
Matched Country Groups: