Lecco vs Lumezzane: match statistics

Lecco are the favorites for this fixture: they sit 3rd in the table versus Lumezzane’s 7th, with 18 wins this season compared to the opponent’s 13, 45 goals scored versus 40 and 29 conceded versus 36. At home Lecco average 1.17 goals scored and concede 0.78 per match, while Lumezzane average 1.00 scored and 1.11 conceded on the road, giving the hosts a defensive edge of approximately 0.33 goals. The hosts also dominate possession (58% vs 47%) and generate more shots (on average 10.82 with 3.94 on target at home vs 9.5 with 3.5 for the away side); Lecco’s xG 1.36 vs Lumezzane’s xG 1.28 confirms the higher quality of the hosts’ chances. In the last 5 matches Lecco have 3 wins, 1 draw and 1 loss (averaging 2.0 points per game), while Lumezzane are unbeaten with 3 wins and 2 draws (averaging 2.2 points per game) and 7 goals in those 5 games, but the visitors have a negative away goal differential of -2 whereas Lecco have +7 at home. Considering the superior seasonal record, stronger home defensive numbers (0.78 goals conceded and 50% clean sheets) and the advantages in possession and shots, I favour a Lecco win, although a draw remains a realistic outcome given Lumezzane’s good form.

Both teams possess significant attacking potential: Lecco generates xG 1.44 and averages 9.67 shots per match with 3.5 on target, while Lumezzane has xG 1.28 and 9.5 shots with 3.5 on target, indicating a realistic chance of goals from both sides. Defensively both allow a lot of chances according to xG: xG against is 1.74 (Lecco) and 1.69 (Lumezzane), which is notably higher than their seasonal actual goals conceded averages of 0.89 and 1.11, suggesting vulnerability to conceding. Historical BTTS rates are moderate — season BTTS is 56% (Lecco) and 44% (Lumezzane) versus a league average of 50%, and in the last 5 matches BTTS was 40% (Lecco) and 60% (Lumezzane), giving a slight edge to the Both Teams To Score - Yes scenario. Additionally, in the last 5 matches Lecco scored 1.8 and conceded 0.6 on average, while Lumezzane scored 1.4 and also conceded 0.6, indicating offensive form from both teams with some defensive resilience. Considering the high xG against (1.74 and 1.69), the season BTTS comparison (56% vs 44%) and recent form (1.8 vs 1.4 goals), I assess BTTS - Yes probability at 60% and No at 40%.

I expect a combined xG of about 3.08 (xG Lecco 1.57 vs xG Lumezzane 1.51), which favors an Over 2.5 goals outcome. This season Lecco has 67% of matches with over 1.5 goals, Lumezzane 61%, while both teams have only 33% of matches over 2.5 goals; however, in the last 5 fixtures both sides have averaged 3.2 goals combined (Lecco 1.8, Lumezzane 1.4). Shot stats show 9.67 shots and 3.5 on target for Lecco with a 13% conversion, and 9.5 and 3.5 for Lumezzane with an 11% conversion; additionally Lumezzane conceded an xG against of 2.01 in their last 5 matches, meaning they have been giving up many chances. Therefore my strongest signal is Over 1.5, because the historical 67%/61% over 1.5 and the projected 3.08 goals provide a clear probability above 1.5 goals; Over 2.5 has a moderate edge (~62%), while Over 3.5 remains unlikely.

The most likely scenario is Lecco leading at the break and winning at full-time (1/1) — I assign this outcome a 36% probability. In their last five matches Lecco led at the break in 4 of 5 games (80%) and averaged 1.2 goals by half-time, while Lumezzane averaged 0.4 half-time goals across those five fixtures. Over the season the home side score 1.22 goals per home match versus Lumezzane’s 1.00 away goals, and Lecco posts a higher xG (1.44 versus the visitors’ 1.28), giving them an edge in chance creation. Additionally Lecco perform better in second halves (averaging 1.56 points in second halves with a positive second-half goal difference of +4), and Lumezzane concede most frequently between the 76th and 90th minute (6 goals), so holding or increasing a lead is realistic. For these reasons 1/1 appears the strongest signal; alternative realistic outcomes are X/1 (19%) or Half-Time/Full-Time draw/draw (12%), but that scenario has the next highest numerical support.