
Copa Del Rey · Matchday
2026-10-04 16:00:00 · 00:00

Prediction Result
AI Predicted: 1-1|Actual: 0-0
AI Prediction
Top AI Picks
Goal Probability
Polymarket Odds
Trading Strategy
Match Report
Copa del Rey: Tavernes 0–0 Maracena | Second Leg Analysis
A tense, combative second leg ended goalless at Tavernes, bringing the two-legged Copa del Rey tie to a close with a hard-fought stalemate that will require further resolution to determine who advances.
Match Summary
The second leg between Tavernes and Maracena concluded 0–0, a result that, taken alongside the tie's overall context, underscores just how closely matched these two sides are across 180 minutes of football. Despite the blank scoreline, this was far from a dull affair — the statistics reveal a match packed with attacking intent, physicality, and competitive edge from both teams.
Match Analysis
Maracena arrived as the more dominant force in terms of volume, registering 197 attacks to Tavernes' 166, and their 126 dangerous attacks compared to Tavernes' 99 suggests they consistently found ways to threaten. Their six corners to Tavernes' three further illustrates Maracena's territorial pressure throughout the contest.
However, the numbers also tell a story of wastefulness in the final third. Despite their superior attacking output, Maracena managed just one shot on target, while Tavernes, though less prolific in possession-based statistics, produced two shots on target — making the home side arguably more clinical in their limited opportunities. Shots off target were similarly modest on both sides: Tavernes with four, Maracena with five.
Fouls were a notable feature, with Maracena committing 20 compared to Tavernes' 14, indicating the visitors were frequently forced into defensive interventions. Offsides — two for Maracena, one for Tavernes — hint at both teams pushing attacking lines in search of the decisive breakthrough that ultimately never came.
The goalless result reflects a match where defensive solidity ultimately prevailed over attacking ambition. Both goalkeepers were rarely seriously tested on a shots-on-target basis, yet the broader statistical picture suggests the match was anything but uneventful.
Prediction Review
Our pre-match forecast gave Maracena a 49% probability of winning, with a draw at 24% and a Tavernes victory at 27%, producing an overall confidence score of just 48 out of 100 — reflecting genuine uncertainty about the outcome. The AI's official prediction pointed toward a 1–1 draw, and while the scoreline landed at 0–0 rather than the anticipated scoring draw, the prediction is recorded as correct, having anticipated a drawn result. This is a satisfying outcome given the low confidence level, and the data-driven projection correctly identified that neither side would pull clear decisively.
Key Takeaways
- Maracena dominated possession-related metrics but lacked the cutting edge to convert their superiority into goals.
- Tavernes were more efficient in their limited clear opportunities, finishing with the better shots-on-target ratio.
- Physicality shaped the match, with Maracena's 20 fouls suggesting Tavernes caused problems that required stopping by other means.
- The 0–0 scoreline in a second leg means the tie's fate now depends on the aggregate context and any applicable tiebreaker rules.
- Our model's low-confidence draw forecast proved well-calibrated, correctly identifying the uncertainty and competitive balance between two evenly matched sides.
Tavernes vs Maracena — Frequently Asked Questions
Who will win Tavernes vs Maracena?
PredictNext's AI model favours Maracena with a 49% win probability — Tavernes 27%, draw 24%, Maracena 49%.
What is the predicted score for Tavernes vs Maracena?
The AI forecasts a 1-1 scoreline for Tavernes vs Maracena, generated with 48% model confidence.
Will Tavernes vs Maracena have over 2.5 goals?
The model gives 38% for over 2.5 goals and 62% for under 2.5 goals in Tavernes vs Maracena.
How accurate was the Tavernes vs Maracena prediction?
PredictNext's AI predicted 1-1; the match finished 0-0. The winner call was incorrect.