LaneDiff costs me $50/month to run. If it helped you win a lane, a small tip keeps it alive. 💙

$0 / $50 raised this month

Donate

Xerath vs Tahm Kench

Xerath
You
VS
Tahm Kench

Tap any portrait to switch perspective

Who Wins

  • Pre-6 you win convincingly at all stages because your range advantage means Tahm Kench cannot reach you to stack W, and your E stun stops any gap-close attempt cold; there is no level spike for Tahm Kench that changes this dynamic since he has no dash or long-range engage.
  • Post-6, Tahm Kench's R lets him survive your burst combo once, so you must respect that he can absorb your full rotation and still walk up — do not overcommit to a kill attempt when his R is available.

How to Trade

  • Your optimal trade pattern is to land Q at max range to chip his health, then when he walks up to retaliate, use E to stun him in place and follow with a full Q charge into W; this forces him to either take full damage or burn summoners.
  • Keep moving laterally between abilities so his Q slow does not connect — a stationary Xerath is the only version of you that Tahm Kench can punish.

Wave Control

  • Shove the wave with W to push Tahm Kench under tower, then use the resulting free time to poke him as he last-hits; his melee range means he takes chip damage every time he steps up to CS under tower if you position aggressively at the tower's edge.
  • Avoid freezing the wave in this matchup — a frozen wave near your tower is one of the few scenarios where Tahm Kench can safely walk up and trade without you having room to kite.

Mistakes to Avoid

  • Do not stand still to charge a long Q when Tahm Kench is within his Q slow range — a slowed Xerath who is channeling is exactly the scenario where he closes distance and stacks W for a full trade.
  • Many Xerath players also forget that Tahm Kench's passive gives him significant damage reduction at low health, so do not assume a low-health Tahm Kench is a free kill without verifying his R and passive thresholds.
Created on 08/09/2026
🛠️ Something wrong?