Strictly Necessary
Required for login, session management, account security, device limits, referral functionality and remembering your cookie choice.
| Date | Match | Score |
|---|---|---|
| 06.05.2026 | Cittadella - Lumezzane | 1 : 0 |
| 07.02.2026 | Lumezzane - Cittadella | 1 : 2 |
| 25.09.2025 | Cittadella - Lumezzane | 0 : 1 |
| Date | Match | Score | Res |
|---|---|---|---|
| 06.09.2026 | Cittadella - Lumezzane | 2 - 1 | W |
| 03.09.2026 | Cittadella - Renate | 4 - 1 | W |
| 31.08.2026 | Renate - Cittadella | 0 - 1 | W |
| 22.08.2026 | Cittadella - Pergolettese | 2 - 0 | W |
| 15.08.2026 | Cittadella - Atalanta II | 2 - 2 | D |
| Date | Match | Score | Res |
|---|---|---|---|
| 06.09.2026 | Cittadella - Lumezzane | 2 - 1 | L |
| 30.08.2026 | Lumezzane - Giana Erminio | 1 - 0 | W |
| 22.08.2026 | Ospitaletto - Lumezzane | 2 - 0 | L |
| 15.08.2026 | Lumezzane - Renate | 2 - 2 | D |
| 01.08.2026 | Cremonese - Lumezzane | 0 - 0 | D |
The upcoming match between Cittadella and Lumezzane is scheduled for 06.09.2026 19:00 in Serie C - Girone A. The listed venue is Stadio Pier Cesare Tombolato, Cittadella. 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
Cittadella are in position 6 with 3 points. The stored form sequence is W. Lumezzane are in position 10 with 3 points. The stored form sequence is WL.
Cittadella recorded 5 wins, 4 draws and 1 losses across the last 10 completed matches. The newest-to-oldest result sequence is WWWDWLDWDD. The averages are 1.50 goals scored and 0.90 goals conceded per match. Both teams scored in 50% of those matches, while 30% finished with over 2.5 goals. Lumezzane recorded 4 wins, 4 draws and 2 losses across the last 10 completed matches. The newest-to-oldest result sequence is WLDDLDWDWW. The averages are 1.10 goals scored and 0.70 goals conceded per match. Both teams scored in 30% of those matches, while 30% finished with over 2.5 goals.
Across the last 3 head-to-head matches, Cittadella recorded 2 wins, there were 0 draws, and Lumezzane recorded 1 wins. The average total was 1.67 goals per match. Both teams scored in 33.3% of those matches, while 33.3% finished with over 2.5 goals.
The highest stored values are: Under 2.5 goals — 100%; Under 3.5 goals — 100%; Over 0.5 first-half goals — 50%; Over 1.5 goals — 40%; Both teams to score — 10%. They are statistical indicators and are not automatically converted into a prediction.
The PMV3 model classifies the leading outcome as Cittadella or draw (1X) with 80% confidence. The stored fair probabilities for home, draw and away are 52.83%, 27.21% and 19.96%. The model momentum difference is 32.87 points in favour of Cittadella. The input data quality score is 85/100. The stored price for the selected market is 1.12 with Bet365. The stored estimated EV is -10.35%. Despite the model probability, the price is marked NO_VALUE. The signal is therefore not treated automatically as a value bet.
The discipline profile for Cittadella at home is based on 1 matches. The team averages 1.00 yellow cards, 0.00 red cards and 1.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 0.0%, 0.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 2 of 2 completed matches (100.0% coverage). The discipline profile for Lumezzane away from home is based on 1 matches. The team averages 3.00 yellow cards, 0.00 red cards and 3.00 total cards per match. At least 1, 2, 3, 4 and 5 cards were recorded in 100.0%, 100.0%, 100.0%, 0.0% and 0.0% of those matches respectively, while a red card occurred in 0.0%. Season card data is available for 2 of 2 completed matches (100.0% coverage).
The match between Cittadella and Lumezzane ended 2-1. The game produced 3 goals in total. The first half contained 3 goals. The following review compares the final result only with historical data, the discipline profile, trend values and Premium signals locked before kickoff.
The previous 3 head-to-head meetings averaged 1.67 goals, while this match produced 3. The final scoring profile differed by more than one goal from that average. Across the previous 3 head-to-head meetings, the leading historical direction was No BTTS at 66.7%. The actual outcome for this indicator was BTTS. The final result did not align with that historical profile. Across the previous 3 head-to-head meetings, the leading historical direction was Under 2.5 at 66.7%. The actual outcome for this indicator was Over 2.5. The final result did not align with that historical profile.
Before kickoff, the stored trend indicated No BTTS at 90%. The actual outcome was BTTS. The stored trend was not confirmed by the result. Before kickoff, the stored trend indicated Under 2.5 at 100%. The actual outcome was Over 2.5. The stored trend was not 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 Under 1.5 HT at 90%. The actual outcome was Over 1.5 HT. The stored trend was not confirmed by the result.
Before kickoff, the discipline profile for Cittadella at home was based on 1 matches, with averages of 1 yellow cards, 0 red cards and 1 total cards per match. In this game, Cittadella received 2 yellow cards and 0 red cards, 2 in total. That was 1 cards above the stored average. In the pre-match sample, 3+ cards occurred in 0% of matches, 5+ in 0%, and a red card in 0%. Before kickoff, the discipline profile for Lumezzane away from home was based on 1 matches, with averages of 3 yellow cards, 0 red cards and 3 total cards per match. In this game, Lumezzane received 2 yellow cards and 1 red cards, 3 in total. The total was effectively equal to the stored average. In the pre-match sample, 3+ cards occurred in 100% of matches, 5+ in 0%, and a red card in 0%.
Of 7 verifiable pre-match indicators, 1 aligned with the final result and 6 were not confirmed. This is a post-match verification of data stored before kickoff, not a revision of the analysis after the match ended.