Draw / Alaves 69%
Under 4.5 80%
Our call: Draw · Likely score 1-1
| Home win | Draw | Away win | |
|---|---|---|---|
| Our call | 31% | 35% | 34% |
| Market | 42% -11%p | 31% +4%p | 27% +7%p |
Match overview
- 🏆 Competition · 🇪🇸 ESP La Liga
- 🗓️ Kick-off · 21 August 2026, 04:00 KST
- ⚔️ Fixture · Rayo Vallecano (home) vs Alaves (away)
Recent Form and Tactical Balance
Rayo Vallecano’s recent performances have been marked by a lack of consistency, averaging 1.0 goal scored and 2.0 conceded per game over their last six matches. Alaves, on the other hand, have shown a more structured approach, averaging 1.7 goals scored and 0.7 conceded. Despite these differences, both teams have generated nearly identical expected goals — 1.89 for Rayo and 1.93 for Alaves — indicating that their attacking systems are similarly effective in terms of creating chances.
Shot Volume and Possession Dynamics
Alaves have been far more aggressive in their approach, averaging 18.0 shots per game with 8.0 on target, compared to Rayo’s 6.0 shots and 3.0 on target. This suggests that Alaves have been more dominant in breaking down defenses and maintaining possession, which has been at 52% for them, just slightly ahead of Rayo’s 51%. However, Rayo’s lower shot count may also be influenced by the absence of several key players, which has disrupted their attacking rhythm and overall control of the game.
Impact of Key Absences
Both teams are missing crucial players through injury or suspension. Rayo are without Luiz Felipe, D. Mendez, and others, which could affect their midfield balance and defensive stability. Alaves are missing F. Garces and T. Mendes, which may impact their ability to control the midfield and maintain their high pressing intensity. These absences add an element of unpredictability, as both teams may struggle to maintain their usual patterns of play.
Statistical Parity and the Draw Scenario
The projected win probabilities — 31% for Rayo, 35% for a draw, and 34% for Alaves — suggest that the match is highly balanced. The most likely scoreline, according to the data, is a 1-1 draw. This outcome is supported by the fact that both teams are expected to score, with the match likely to finish under 2.5 goals. The statistical parity in xG, shot volume, and win probabilities all point to a scenario where neither side dominates for long periods, making a draw the most logical conclusion.
What to Watch for
The match will hinge on how well each team adapts to the absence of their key players. Alaves’ defensive record suggests they are more likely to keep a clean sheet, but Rayo’s counter-attacking potential could create opportunities. If either side is unable to maintain their usual structure, the game could become more open. Alaves’ higher shot count may give them an edge in terms of creating chances, but Rayo’s ability to exploit spaces could make the difference in a tightly contested match.
The Call
Given the statistical balance, the recent form, and the projected probabilities, my read is that a draw is the most likely outcome. The numbers point to a 1-1 scoreline, with both teams expected to score and the match finishing under 2.5 goals. However, this prediction would be wrong if Rayo manage to break down Alaves’ defense more effectively than expected, or if Alaves fail to maintain their usual defensive discipline. In either case, the match will likely remain tightly contested, with neither side able to secure a decisive advantage.
Analysis & projection
▶ Our call: Draw · Projected score 1-1
| Home win | Draw | Away win |
|---|---|---|
| 31% | 35% | 34% |
Both teams to score: Yes · Over/Under 2.5: Under
Final result and how the call fared will be added here after the match.
This article is a reference analysis based on public statistics and does not encourage betting. Actual results may differ.
Result & review
🏁 Full-time: Rayo Vallecano 1 : 1 Alaves
| Prediction | Call | Outcome |
|---|---|---|
| Our call | Draw | ✓ Hit |
| Projected score | 1-1 | ✓ Hit |
| Both teams to score | Yes | ✓ Hit |
| Over/Under 2.5 | Under | ✓ Hit |
4/4 of the pre-match calls were correct.