← Back to overall
Pelipper
Appeared 29 times · 26.13% usage · ranked #5
14 tournaments · 111 teams entered
Weekly trend chart
Not enough weekly data
Common Sets
Pelipper
·
WatFly
Drizzle
FlyHurricane
FlyTailwind
NrmWeather Ball
RckWide Guard
37.9%11/29
Pelipper
·
WatFly
Drizzle
FlyHurricane
NrmProtect
FlyTailwind
NrmWeather Ball
27.6%8/29
Pelipper
·
WatFly
Drizzle
FlyHurricane
FlyTailwind
NrmWeather Ball
RckWide Guard
10.3%3/29
Pelipper
·
WatFly
Drizzle
FlyHurricane
NrmProtect
NrmWeather Ball
RckWide Guard
6.9%2/29
Pelipper
·
WatFly
Drizzle
FlyHurricane
IceIcy Wind
WatRain Dance
NrmWeather Ball
3.5%1/29
Pelipper
·
WatFly
Drizzle
NrmHelping Hand
FlyHurricane
FlyTailwind
NrmWeather Ball
3.5%1/29
Ability
- 29/29100.00%
Item (Top 8)
- 16/2955.17%
- 8/2927.59%
- 3/2910.34%
- 1/293.45%
1/293.45%
Moves (Top 10)
- Fly29/29100.00%
- Nrm28/2996.55%
- Fly26/2989.66%
- Rck17/2958.62%
- Nrm12/2941.38%
- 1/293.45%
- 1/293.45%
- 1/293.45%
- 1/293.45%
Teammates
How to read “Usage” and “Synergy”
“Usage” = how many teams run it; “Synergy” = whether they're brought together on purpose.
| Lift | Usage | Meaning |
|---|---|---|
| Low | High | Generic staple: pairs with everyone; high usage just reflects its own popularity, not a special bond. |
| 2~3 | High | Mainstream pairing: a common, strong combo. |
| High | Low | Niche locked combo: rarely used overall, but those who use it almost always run them together. |
Details
Synergy (Lift) = actual co-occurrence ÷ co-occurrence expected from each Pokémon's solo usage. It tells you whether a combo is brought together on purpose, vs both just being popular.
< 1Anti-synergy: overlapping or competing roles — running one means skipping the other.
≈ 1Coincidence: both just popular, happen to share teams, no real link.
1~5Paired more than random — the higher it climbs, the more deliberate the pairing.
5+Tight core: see one and the other is usually there too (e.g. weather setter + abuser).
- A very high synergy usually just means the members are individually rare (low solo usage), not that the pairing is strong; read it alongside usage %, and don't compare synergy across combos with different usage.
