
Cookies: one sign-in cookie. Analytics only if you accept. Cookie policy
Photo: Sandrino 14, CC BY-SA 4.0H2H ENCYCLOPEDIA
League meetings, 2012/13 to 2018/19 · from OneTouch's results archive
Home wins
3
Draws
1
Avg goals / game
1.8
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 |
|---|---|---|---|---|
| 29 Mar 2019 | Serie A | Cagliari 3–0 ChievoVerona | +3 | W |
| 28 Oct 2018 | Serie A | Cagliari 2–1 ChievoVerona | +1 | W |
| 17 Feb 2018 | Serie A | Cagliari 1–2 ChievoVerona | +1 | L |
| 24 Sept 2017 | Serie A | Cagliari 0–2 ChievoVerona | +2 | L |
| 15 Apr 2017 | Serie A | Cagliari 4–0 ChievoVerona | +4 | W |
| 19 Nov 2016 | Serie A | Cagliari 0–1 ChievoVerona | +1 | L |
| 29 Apr 2015 | Serie A | Cagliari 0–1 ChievoVerona | +1 | L |
| 08 Dec 2014 | Serie A | Cagliari 0–2 ChievoVerona | +2 | L |
| 11 May 2014 | Serie A | Cagliari 0–1 ChievoVerona | +1 | L |
| 05 Jan 2014 | Serie A | Cagliari 0–0 ChievoVerona | — | D |
BIGGEST WINS — HOME SIDE
Largest winning margins from the encyclopedia's home perspective, over the full tracked ledger.
Cagliari 4–0 ChievoVerona
Serie A · 15 Apr 2017
Cagliari 3–0 ChievoVerona
Serie A · 29 Mar 2019
Cagliari 2–1 ChievoVerona
Serie A · 28 Oct 2018
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.
Cagliari 0–2 ChievoVerona
Serie A · 24 Sept 2017
Cagliari 0–2 ChievoVerona
Serie A · 08 Dec 2014
Cagliari 0–2 ChievoVerona
Serie A · 09 Dec 2012
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.