
Cookies: one sign-in cookie. Analytics only if you accept. Cookie policy
Photo: Asgaw, CC BY-SA 4.0H2H ENCYCLOPEDIA
League meetings, 2012/13 to 2018/19 · from OneTouch's results archive
Home wins
5
Draws
3
Avg goals / game
2.1
Current streak
2W
LAST MEETINGS
Most recent first, signed from the pair's home perspective. Goal margins are net wins/losses for the encyclopedia home side.
| Date | Competition | Score | Margin | Result |
|---|---|---|---|---|
| 03 Mar 2019 | Serie A | Torino 3–0 ChievoVerona | +3 | W |
| 30 Sept 2018 | Serie A | Torino 1–0 ChievoVerona | +1 | W |
| 14 Apr 2018 | Serie A | Torino 0–0 ChievoVerona | — | D |
| 19 Nov 2017 | Serie A | Torino 1–1 ChievoVerona | — | D |
| 23 Apr 2017 | Serie A | Torino 3–1 ChievoVerona | +2 | W |
| 26 Nov 2016 | Serie A | Torino 2–1 ChievoVerona | +1 | W |
| 07 Feb 2016 | Serie A | Torino 1–2 ChievoVerona | +1 | L |
| 23 Sept 2015 | Serie A | Torino 0–1 ChievoVerona | +1 | L |
| 17 May 2015 | Serie A | Torino 2–0 ChievoVerona | +2 | W |
| 06 Jan 2015 | Serie A | Torino 0–0 ChievoVerona | — | D |
BIGGEST WINS — HOME SIDE
Largest winning margins from the encyclopedia's home perspective, over the full tracked ledger.
Torino 3–0 ChievoVerona
Serie A · 03 Mar 2019
Torino 4–1 ChievoVerona
Serie A · 22 Dec 2013
Torino 3–1 ChievoVerona
Serie A · 23 Apr 2017
BIGGEST LOSSES — HOME SIDE
Largest winning margins for the away side from the encyclopedia's home perspective — i.e. the heaviest defeats for the home side.
Torino 1–2 ChievoVerona
Serie A · 07 Feb 2016
Torino 0–1 ChievoVerona
Serie A · 23 Sept 2015
METHODOLOGY
Every row on this page comes straight from api-football’s /fixtures/headtohead endpoint, filtered to confirmed final scores (status=FT). Goal deltas are net wins/losses for the encyclopedia’s home side, so a positive margin always means an actual win for that team.
Where the provider can’t resolve a historical meeting, the page falls back to a clean “no record” state rather than fabricate incomplete numbers.
Top-scorers panel intentionally omitted in v1 — would require fabricated per-fixture scorer history that the provider doesn’t return.