Match context

The upcoming match between Tigre and Belgrano Cordoba is scheduled for 06.08.2026 00:15 in Liga Profesional Argentina. The analysis uses only stored statistics, form, head-to-head records, trend percentages and active Premium market signals. It does not guarantee a particular result.

Standings and season form
Tigre are in position 11 with 3 points after 18 matches. The season record is 5 wins, 8 draws and 5 losses. The goals record is 21 scored and 17 conceded. The stored form sequence is WLDLD. Belgrano Cordoba are in position 12 with 3 points after 22 matches. The season record is 12 wins, 5 draws and 5 losses. The goals record is 27 scored and 18 conceded. The stored form sequence is LWWWW.

Recent results

Tigre recorded 4 wins, 3 draws and 3 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLLWLWDDDW. The averages are 1.50 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals. Belgrano Cordoba recorded 6 wins, 2 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is LWDWDWWWLW. The averages are 1.60 goals scored and 0.80 goals conceded per match. Both teams scored in 40% of those matches, while 40% finished with over 2.5 goals.

Head-to-head

Across the last 10 head-to-head matches, Tigre recorded 3 wins, there were 5 draws, and Belgrano Cordoba recorded 2 wins. The average total was 2 goals per match. Both teams scored in 50% of those matches, while 40% finished with over 2.5 goals.

Trend indicators

The highest stored values are: Under 3.5 goals — 100%; Over 0.5 first-half goals — 60%; Over 1.5 goals — 60%; Under 2.5 goals — 60%; Over 1.5 first-half goals — 40%. They are statistical indicators and are not automatically converted into a prediction.

Asian handicap market movement

The normalized movement for the Asian pair Tigre -1 / Belgrano Cordoba +1 supports Tigre by an average 4.08 percentage points across 3 bookmakers (Pinnacle, Bet365, 1xBet) with up to 21 stored observations. This is a market signal, not a result guarantee.

What happened in the match

The match between Tigre and Belgrano Cordoba ended 0-0. The game produced 0 goals in total. The first half contained 0 goals. The following review compares the final result only with historical data, trend values and Premium signals locked before kickoff.

Comparison with the head-to-head history

The previous 10 head-to-head meetings averaged 2 goals, while this match produced 0. The final scoring profile differed by more than one goal from that average. Across the previous 10 head-to-head meetings, the leading historical direction was Under 2.5 at 60%. The actual outcome for this indicator was Under 2.5. The final result aligned with that historical profile.

Which pre-match trends were confirmed and which were not

Before kickoff, the stored trend indicated No BTTS at 80%. The actual outcome was No BTTS. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 1.5 at 60%. The actual outcome was Under 1.5. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 60%. The actual outcome was Under 2.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Under 3.5 at 100%. The actual outcome was Under 3.5. The stored trend was confirmed by the result. Before kickoff, the stored trend indicated Over 0.5 HT at 60%. The actual outcome was Under 0.5 HT. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 1.5 HT at 60%. The actual outcome was Under 1.5 HT. The stored trend was confirmed by the result.

Asian handicap review

The Asian-handicap signal locked before kickoff supported Tigre at -1. The stored market movement was 4.08 percentage points across 3 bookmakers. At the final score of 0-0, the line settled as a full loss. The Asian-handicap signal was not confirmed.

Summary

Of 9 verifiable pre-match indicators, 5 aligned with the final result and 4 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.