Alistar vs Yuumi — Support Lane Matchup Guide
You
Alistar
Opponent
Yuumi
Your ranked stats
50.0%
Win rate
4.0%
Pick rate
2.0%
Ban rate
2.54
KDA
C
Tier
#115
Rank
Opponent stats
47.0%
Win rate
5.0%
Pick rate
7.0%
Ban rate
4.30
KDA
D
Tier
#165
Rank
A level-by-level game plan for Alistar vs Yuumi.
Levels 1-2
Your job is to win the 2v2 without dying, not necessarily to get kills yourself.
- Alistar should soak poke and hold lane priority through durability, not even trades.
- Respect their engage range in the 2v2 — don't overextend without knowing their cooldowns.
- OP.GG data flags Yuumi as a strong counter to Alistar in this role — expect them to look for early trades, so play a touch safer than usual.
Levels 3-5
Trade when your ADC has priority, and hold cooldowns to punish overextensions.
- Look for CC chains that let your jungler or teammates punish overextensions.
- Their utility can swing an even trade against you — bait cooldowns before an all-in.
Level 6
Jungler ganks and bot lane all-ins both spike here — play safer without vision.
- Your ultimate usually turns you into a real engage or peel threat — use it on your terms.
- Their ultimate can turn a losing fight around — assume they have a trick even when behind.
Levels 7-11
Roaming and vision control around dragon become your biggest source of impact.
- Front line for your team around objectives so your carries can output freely.
- They'll roam to set up picks — track wards and avoid walking through unwarded areas alone.
Levels 12-15
Your item spike decides whether you peel, engage, or poke in fights.
- Tank items complete — you should be nearly unkillable while still landing your CC.
- Utility spikes let them enable big plays — expect a coordinated engage around objectives.
Level 16+
You decide when fights start — vision and positioning matter more than stats.
- You start most teamfights and decide their shape — landing your engage matters most.
- They decide when the fight starts — don't give them a clean engage on your carries.
OP.GG data as of Jul 13, 2026 · patch 16.13.1