Current League Standings | P | GD | PTS | |
11 | Belshina | 10 | -3 | 11 |
12 | Torpedo-BelAZ | 9 | -6 | 8 |
13 | Vitebsk | 10 | -8 | 7 |
Current League Standings | P | GD | PTS | |
2 | Energetik-BGU | 10 | 15 | 22 |
3 | Dinamo Minsk | 10 | 6 | 21 |
4 | FC Minsk | 10 | 4 | 19 |
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 Dinamo Minsk win with a probability of 49.23%. A draw had a probability of 26.6% and a win for Torpedo-BelAZ had a probability of 24.21%.
The most likely scoreline for a Dinamo Minsk win was 0-1 with a probability of 13.32%. The next most likely scorelines for that outcome were 0-2 (9.7%) and 1-2 (9.07%). The likeliest drawn scoreline was 1-1 (12.46%), while for a Torpedo-BelAZ win it was 1-0 (8.56%). The actual scoreline of 3-4 was predicted with a 0.2% likelihood. Our data analysis correctly predicted that Dinamo Minsk would win this match.
Result | ||
Torpedo-BelAZ | Draw | Dinamo Minsk |
24.21% ( 0.03) | 26.56% ( 0.03) | 49.23% ( -0.06) |
Both teams to score 46.58% ( -0.06) |
Goals |
Over 2.5 | Under 2.5 |
42.79% ( -0.09) | 57.21% ( 0.09) |
Over 3.5 | Under 3.5 |
21.94% ( -0.07) | 78.06% ( 0.08) |
Torpedo-BelAZ Goals |
Over 0.5 | Under 0.5 |
60.74% ( -0.03) | 39.26% ( 0.03) |
Over 1.5 | Under 1.5 |
24.03% ( -0.03) | 75.97% ( 0.03) |
Dinamo Minsk Goals |
Over 0.5 | Under 0.5 |
76.68% ( -0.06) | 23.32% ( 0.07) |
Over 1.5 | Under 1.5 |
42.73% ( -0.1) | 57.27% ( 0.1) |
Score Analysis |
Torpedo-BelAZ | Draw | Dinamo Minsk |
1-0 @ 8.56% ( 0.02) 2-1 @ 5.83% ( 0) 2-0 @ 4% ( 0.01) 3-1 @ 1.82% ( -0) 3-2 @ 1.32% ( -0) 3-0 @ 1.25% ( 0) Other @ 1.44% Total : 24.22% | 1-1 @ 12.46% ( 0.01) 0-0 @ 9.15% ( 0.03) 2-2 @ 4.24% ( -0.01) Other @ 0.7% Total : 26.56% | 0-1 @ 13.32% ( 0.02) 0-2 @ 9.7% ( -0) 1-2 @ 9.07% ( -0.01) 0-3 @ 4.71% ( -0.01) 1-3 @ 4.4% ( -0.01) 2-3 @ 2.06% ( -0.01) 0-4 @ 1.71% ( -0.01) 1-4 @ 1.6% ( -0.01) Other @ 2.64% Total : 49.22% |
ISOCountry Code:
Matched Country Groups: