
Cookies: one sign-in cookie. Analytics only if you accept. Cookie policy
H2H ENCYCLOPEDIA
League meetings, 2010/11 to 2018/19 · from OneTouch's results archive
Home wins
0
Draws
3
Avg goals / game
3.8
Current streak
1L
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 |
|---|---|---|---|---|
| 10 Mar 2019 | Bundesliga | Hannover 96 2–3 Bayer Leverkusen | +1 | L |
| 20 Oct 2018 | Bundesliga | Hannover 96 2–2 Bayer Leverkusen | — | D |
| 12 May 2018 | Bundesliga | Hannover 96 2–3 Bayer Leverkusen | +1 | L |
| 17 Dec 2017 | Bundesliga | Hannover 96 4–4 Bayer Leverkusen | — | D |
| 30 Jan 2016 | Bundesliga | Hannover 96 0–3 Bayer Leverkusen | +3 | L |
| 22 Aug 2015 | Bundesliga | Hannover 96 0–1 Bayer Leverkusen | +1 | L |
| 18 Apr 2015 | Bundesliga | Hannover 96 0–4 Bayer Leverkusen | +4 | L |
| 22 Nov 2014 | Bundesliga | Hannover 96 1–3 Bayer Leverkusen | +2 | L |
| 08 Mar 2014 | Bundesliga | Hannover 96 1–1 Bayer Leverkusen | — | D |
| 28 Sept 2013 | Bundesliga | Hannover 96 0–2 Bayer Leverkusen | +2 | L |
BIGGEST WINS — HOME SIDE
Largest winning margins from the encyclopedia's home perspective, over the full tracked ledger.
Hannover 96 3–2 Bayer Leverkusen
Bundesliga · 09 Dec 2012
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.
Hannover 96 0–4 Bayer Leverkusen
Bundesliga · 18 Apr 2015
Hannover 96 0–3 Bayer Leverkusen
Bundesliga · 30 Jan 2016
Hannover 96 1–3 Bayer Leverkusen
Bundesliga · 22 Nov 2014
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.