Home › League stats › Copa do Brasil U17
Brazil
Copa do Brasil U17 statistics and predictions
Season to date: 13 matches since 28 Apr 2026, last updated 30 Oct 2026.
Copa do Brasil U17 in numbers
Analysis
13 matches have been played in the Copa do Brasil U17 (Brazil) since 28 Apr 2026, averaging 3.92 goals a game. That makes it a higher-scoring competition than the average across our archive (3.07 goals a game).
Home sides won 5 (38%), 3 matches were drawn (23%) and away sides won 5 (38%). Home advantage here is weaker than usual. Both teams scored in 38% of matches, 69% went over 2.5 goals, 92% over 1.5, and 0 finished goalless.
Our team-strength model, refitted every night, rates the strongest attacks as Atlético Mineiro U17 (1.17), Cruzeiro U17 (1.17), Athletico PR U17 (1.10), and the meanest defences as Cruzeiro U17 (0.68), Atlético Mineiro U17 (0.70), Athletico PR U17 (0.88). A rating of 1.00 is an average side in this competition.
Results table
Calculated from the final scores in our archive since 28 Apr 2026. This is not the official table — it applies no points deductions or tie-break rules, and for cup competitions it simply totals results across rounds.
| # | Team | P | W | D | L | GF | GA | GD | Pts |
|---|---|---|---|---|---|---|---|---|---|
| 1 | Athletico PR U17 | 5 | 3 | 2 | 0 | 15 | 4 | 11 | 11 |
| 2 | Atlético Mineiro U17 | 5 | 3 | 2 | 0 | 11 | 5 | 6 | 11 |
| 3 | Cruzeiro U17 | 4 | 2 | 1 | 1 | 11 | 3 | 8 | 7 |
| 4 | Coritiba U17 | 4 | 2 | 0 | 2 | 12 | 7 | 5 | 6 |
| 5 | Fortaleza U17 | 2 | 0 | 1 | 1 | 1 | 2 | -1 | 1 |
| 6 | Monte Roraima U17 | 2 | 0 | 0 | 2 | 1 | 10 | -9 | 0 |
| 7 | CSA U17 | 2 | 0 | 0 | 2 | 0 | 10 | -10 | 0 |
| 8 | IAPE U17 | 2 | 0 | 0 | 2 | 0 | 10 | -10 | 0 |
About these statistics
The figures above are counts over final scores (90 minutes) in the PunterPick results archive. Nothing is estimated: a match only counts once its final score is in. Team links lead to each side's own form, home and away record and the predictions we have published for them. How we build our predictions is explained on the methodology page.