?
GLuck Yungstar 2026 Series 3 · BO3
result vs prediction
VP.Futureloss 0:2
series probability
38%62%
probability at match start · final 0:2
QUAZAR#99 in the world · win 2:0
The prediction was locked in using data as of the match start: map winrates, form and head-to-head were computed only from games before it began. This is how the model's honest accuracy is verified.
Map veto prediction
For each map — both teams' winrate over 3 months. The model guesses who bans it and who keeps it: teams remove maps where they are weaker and pull toward their strong ones.
Dust2QUAZAR ban
43%44%
VP.Future · 3 mapsnearly even -1%QUAZAR · 14 maps
CacheVP.Future ban
50%67%
VP.Future · 0 mapsedge QUAZAR +17%QUAZAR · 14 maps
MirageVP.Future ban
60%59%
VP.Future · 1 mapnearly even +1%QUAZAR · 13 maps
AnubisQUAZAR ban
60%54%
VP.Future · 1 mapedge VP.Future +6%QUAZAR · 9 maps
NukeQUAZAR pick
50%64%
VP.Future · 0 mapsedge QUAZAR +14%QUAZAR · 10 maps
InfernoVP.Future pick
50%55%
VP.Future · 2 mapsedge QUAZAR +5%QUAZAR · 7 maps
Most likely veto scenario
1. BanVP.Future remove Cache
2. BanQUAZAR remove Dust2
3. PickVP.Future take Inferno
4. PickQUAZAR take Nuke
5. BanQUAZAR remove Anubis
6. BanVP.Future remove Mirage
Prediction by map vs result
Probabilities were locked in using statistics as of the match start (map winrate over the 3 months before it). We compare against the actual result of each map.
Dust2prediction missed3:13
VP.Future 51%QUAZAR 49%
The model gave 51% on VP.Future — the map was taken by QUAZAR.
Mirageprediction correct10:13
VP.Future 48%QUAZAR 52%
The model gave 52% on QUAZAR — the map was taken by QUAZAR.
Model check result
Model favoriteQUAZAR · 62%
Series resultQUAZAR 0:2
Series predictioncorrect
Accuracy by map1 of 2