Skip to content
PoGoBattler

Not in raids nowNo announced raid window, Max Battle event or Power Spot board includes this species. Simulate it anyway · What is in raids

Alolan Persian

#0053
Attack
158
Defense
136
Stamina
163
Best fast:
Feint Attack 13.20 DPS with STAB
Best charged:
Dark Pulse 1.92 DPE with STAB
Max CP:
2,026

In-game artwork for this exact form (PokeMiners asset dump).

FormsPersianAlolan Persian
Slug:
persian-alola
Game Master form:
PERSIAN_ALOLA
Family:
FAMILY_MEOWTH

Base stats and CP

Straight from the Game Master; CP uses the level 1 to 51 CPM table. Ranks are recomputed over the released forms in the snapshot on every render.

Attack#643 of 1,123 · top 57.3%
158
Defense#642 of 1,123 · top 57.2%
136
Stamina#578 of 1,123 · top 51.5%
163

Stat product 3,502,544 — #663 of 1,123 released forms. Bars are scaled against the highest value in the snapshot, not a round number.

Max CP (L40)
1,771
15/15/15, old level cap
Max CP (L50)
2,002
15/15/15, current level cap
Max CP (L51)
2,026
15/15/15 best buddy — Pokebattler's headline
Catch CP (L20)
952 - 1,012
IV 10 to 15
Catch CP (L25)
1,191 - 1,265
weather boosted, IV 10 to 15

Evolution family

1 evolution in this line, with the candy and everything else the game asks for — read out of the Game Master's evolutionBranch, form by form.

  1. Base
  2. Stage 2
    Alolan Persian158/136/163 · 1,771 CP
    50 candy
    • 45 candy once purified

Evolutions are form-accurate: a regional form evolves into its own regional form, and a branch the game does not have is not drawn (Alolan Raichu names Pikachu as its parent but is not what Pikachu evolves into, so no line is shown). Mega Evolution is not part of this family — it costs Mega Energy and reverts, so it sits with the forms above.

In the field

Buddy, Pokedex and unlock numbers, all read from this form's own Game Master template.

Buddy distance
3 km
walked per candy
Height
1.1 m
Weight
33 kg
Second charged move
50 candy
50,000 stardust
Shadow move
Frustration
Return once purified

Best against

Which raid bosses Alolan Persian is a top counter for, aggregated over the 123 bosses on the roster the same way pokebattler.com aggregates its own attacker rankings.

Alolan Persian does not reach the top 32 against any of the 123 bosses on the roster, with or without Shadow, Mega and Legendary attackers in the pool. That is an honest "no", not a missing measurement — it was ranked against every one of them.

Run it against a specific boss anyway →

As a raid boss (Tier 1)

Boss stats use 15/15/15 IVs, the tier CP multiplier and the tier's fixed HP pool.

Lobby CP
5,207
Attack
103
Defense
90
HP
600

Not in the current raid rotation snapshot. The counters below are still exact for the tier this form would be hosted at.

Best counters against Alolan Persian →

Catch CP after the raid

IV spreadCP at L20CP at L25 (weather boosted)
10/10/10floor9521,191
11/11/119641,205
12/12/129761,220
13/13/139881,235
14/14/141,0001,250
15/15/15hundo1,0121,265

Caught CP range 952 - 1,012, or 1,191 - 1,265 when the weather boosts it.

A raid encounter is level 20 (level 25 weather boosted) and cannot roll an IV below 10/10/10. Anything outside the first range is not this raid's reward.

Type matchups

Every one of the 18 attacking types against this typing. GO multipliers: 1.6x super effective, 0.625x resisted, 0.390625x doubly resisted.

  • Weak (3)
  • Neutral (12)
  • Resists (3)
Weak to
Resists

Every tile and chip is a link: it opens the Pokedex filtered to that type, so a weakness leads straight to the attackers that exploit it. Pokebattler lists only the weaknesses; the eleven types that do neither matter as much to a raider deciding what to bring, so all 18 are shown with the exact multiplier.

Same typing, same matchups

Released dark forms with the highest attack — they share every weakness and resistance above.

Movepool

2 fast and 5 charged moves, elite / legacy included. Ranked by damage per second (fast) and damage per energy (charged), both with this form's x1.2 STAB applied where it earns it.

Best moveset21.4 DPS

5 x Feint Attack per Foul Play · 7.0s cycle · 150 power with STAB

#220.5 DPS

10 x Feint Attack per Payback · 12.0s cycle · 246 power with STAB

#320.3 DPS

5 x Feint Attack per Dark Pulse · 8.0s cycle · 162 power with STAB

Fast moves

MoveTypePowerEnergyDurationDPSEPSSource
Feint AttackSTABdark11+101.0s13.2010.00standard
Scratchnormal6+40.5s12.008.00standard

Charged moves

MoveTypePowerEnergyDurationDPSDPESource
Dark PulseSTABdark80-503.0s32.001.92standard
Play Roughfairy90-503.0s30.001.80standard
Foul PlaySTABdark70-502.0s42.001.68standard
Trailblazegrass65-502.0s32.501.30standard
PaybackSTABdark95-1002.0s57.001.14standard

STAB marks moves that share a type with this form (x1.2 damage), and the DPS and DPE columns above already have that x1.2 in them — so a STAB move and a stronger-on-paper neutral move can be compared straight down the column, which is how the best-moveset cards rank them too. Power and Duration stay raw; hover a DPS or DPE figure to see the arithmetic. Att DPS and Def DPS are the two columns pokebattler.com prints in the same table, reproduced exactly: both are raw with no STAB, Def DPS is power / duration, and Att DPS is power / (duration + 2s), the gym move delay. They are there so this table can be diffed against theirs row by row — every row on the pages read on 2026-09-11 matches. Energy is gained on fast moves and spent on charged moves. Every move name opens its own page with the damage window and every other form that learns it — or browse all moves.

Trainer Battles

The same moves, on the Trainer Battle clock: 0.5s per turn, 100 energy cap, stat changes included. These numbers come from a separate Game Master template and are not the raid numbers above.

Best pairing10.2DPT

Feint Attack+Payback

10 fast throws · 20 turns · 10.0s to fire

#29.2DPT

Feint Attack+Foul Play

7 fast throws · 14 turns · 7.0s to fire

#38.9DPT

Feint Attack+Dark Pulse

9 fast throws · 18 turns · 9.0s to fire

Fast moves

MoveTypePowerEnergyTurnsDPTEPT
Scratchnormal4+21(0.5s)4.002.00
Feint AttackSTABdark6+62(1.0s)3.603.00

Charged moves

MoveTypePowerEnergyDPEEffect
PaybackSTABdark110-602.20none
Foul PlaySTABdark65-401.95none
Dark PulseSTABdark80-501.92none
Play Roughfairy90-601.50none
Trailblazegrass65-451.44self Atk +1

Turns are the one-based count the game and every reference site print: the Game Master ships a zero-based durationTurns, so its 1 is a 2-turn move. DPT and EPT are damage and energy per turn and DPE is damage per energy, both with this form's x1.2 STAB already in them where the row is flagged STAB, so the columns can be read straight down; Power and Energy stay raw. A stat change moves the target up or down the game's own ladder (0.50, 0.57, 0.67, 0.80, 1.00, 1.25, 1.50, 1.75, 2.00 for stages -4 to +4). Every Trainer Battle number is audited on the data-quality page.

Acquisition and variants

Shadow and Purified

Available as a Shadow Pokemon (x1.2 attack, x0.833 defense). Shadow charged move FRUSTRATION, purified RETURN.

Second charged move

50,000 Stardust and 50 Candy.

Max Battles

Cannot Dynamax.

Mega Evolution

This entry is not a Mega or Primal form.

Forms of Persian (2)

Every form the snapshot carries for this dex number. Each one appears exactly once.

FormTypesAtkDefStaMovesStatus
Persiannormal1501361632f / 5creleased
Alolan Persiandark1581361632f / 5creleased

Where this data comes from

Every field above is read from the committed snapshot, never typed by hand.

Built 2026-10-03 from the PokeMiners Game Master (https://raw.githubusercontent.com/PokeMiners/game_masters/master/latest/latest.json) by npm run data:build.

No hand-curated correction was needed for this form; it comes straight from the Game Master template.

Checked against Pokebattler1 movepool difference

Their entry: PERSIAN_ALOLA_FORM — 2 fast, 6 charged. Ours: 2 fast, 5 charged.

  • Return (charged) — only on Pokebattler: Return (purified only)

Source: https://fight.pokebattler.com/pokemon, read 2026-10-03. The full diff across all 1,269 forms is on the movepool cross-check.

Snapshot integrity is re-checked on every build and on the data quality page.