Current League Standings | P | GD | PTS | |
1 | Shandong Taishan | 10 | 11 | 24 |
2 | Henan Songshan Longmen | 10 | 14 | 23 |
3 | Shanghai Shenhua | 9 | 7 | 20 |
Current League Standings | P | GD | PTS |
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 Wuhan Three Towns win with a probability of 55.66%. A draw had a probability of 24.8% and a win for Henan Songshan Longmen had a probability of 19.59%.
The most likely scoreline for a Wuhan Three Towns win was 0-1 with a probability of 13.69%. The next most likely scorelines for that outcome were 0-2 (11.11%) and 1-2 (9.44%). The likeliest drawn scoreline was 1-1 (11.63%), while for a Henan Songshan Longmen win it was 1-0 (7.17%). The actual scoreline of 0-3 was predicted with a 6% likelihood. Our data analysis correctly predicted that Wuhan Three Towns would win this match.
Result | ||
Henan Songshan Longmen | Draw | Wuhan Three Towns |
19.59% ( -0.28) | 24.75% ( -0.06) | 55.66% ( 0.34) |
Both teams to score 45.95% ( -0.25) |
Goals |
Over 2.5 | Under 2.5 |
44.91% ( -0.11) | 55.09% ( 0.11) |
Over 3.5 | Under 3.5 |
23.65% ( -0.09) | 76.35% ( 0.09) |
Henan Songshan Longmen Goals |
Over 0.5 | Under 0.5 |
57.24% ( -0.38) | 42.76% ( 0.38) |
Over 1.5 | Under 1.5 |
20.91% ( -0.33) | 79.08% ( 0.32) |
Wuhan Three Towns Goals |
Over 0.5 | Under 0.5 |
80.26% ( 0.09) | 19.74% ( -0.09) |
Over 1.5 | Under 1.5 |
48.24% ( 0.15) | 51.76% ( -0.15) |
Score Analysis |
Henan Songshan Longmen | Draw | Wuhan Three Towns |
1-0 @ 7.17% ( -0.05) 2-1 @ 4.94% ( -0.07) 2-0 @ 3.05% ( -0.05) 3-1 @ 1.4% ( -0.03) 3-2 @ 1.14% ( -0.02) Other @ 1.89% Total : 19.59% | 1-1 @ 11.63% ( -0.04) 0-0 @ 8.44% ( 0.04) 2-2 @ 4.01% ( -0.04) Other @ 0.67% Total : 24.75% | 0-1 @ 13.69% ( 0.1) 0-2 @ 11.11% ( 0.11) 1-2 @ 9.44% ( -0) 0-3 @ 6.01% ( 0.08) 1-3 @ 5.11% ( 0.01) 0-4 @ 2.44% ( 0.04) 2-3 @ 2.17% ( -0.02) 1-4 @ 2.07% ( 0.01) Other @ 3.62% Total : 55.66% |
ISOCountry Code:
Matched Country Groups: