Ranger Wiki · Unofficial

Rayquaza

From the Pokemon Ranger Wiki · Browser No. 210 · Pokemon Ranger (DS, 2006)

Rayquaza takes 13 loops to capture in Pokemon Ranger. The game's maps never place it; what is known about where you meet it is below. Its Poke Assist, Flying, is never usable in play, and it has no field move. It is in this game only.

In Pokemon Ranger, Rayquaza takes 13 loops at any Styler level, and 18 Pokemon in that game take more. Source 1: Cross-checked The hardest captures in all three games.

In the Ranger series

Rayquaza is in the Browser of one of the three Ranger games.

GameBrowser number
Pokemon Ranger (2006)No. 210 Source 4: From the game
Shadows of Almia (2008)Not in the Browser Source 5: From the game
Guardian Signs (2010)Not in the Browser Source 6: From the game

Pokemon Ranger (DS, 2006): every section below covers this game.

How Rayquaza moves

The capture field moves Rayquaza by these numbers, drawn with the game's own field sprite and animations. Source 7: From the game

WhatRayquazaSource
MovementWalks to each stop, turning as it goes (movement type 36).Source 8: From the game
Turn speedUp to about 5.6 degrees a frame, always the short way round (game value 400).Source 9: From the game
Walk speedAbout 0.94 pixels a frame (game value 480).Source 8: From the game, value unconfirmedSource 10: Best reading (unconfirmed), pixels
Run speedGame value 64 a frame, for fast walks and some special actions.Source 8: From the game
Where it walks nextA random spot 16 to 128 pixels away, inside field area 3 (x 18 to 237, y 90 to 179); it tries up to 8 times, then takes the last.Source 8: From the game
RestsNever (its rest time is 0, with no random extra)Source 11: From the game
TurningTurns while it walks; stops to turn only near its stop, when 45 degrees or more off course.Source 8: From the game
Special actionA shooting run: it runs to a new spot and fires as it goes. A 60 percent chance each time it decides, never during a cooldown.Source 12: From the game, chance and type Source 13: From the game, what the type does
At the startWalks at once.Source 12: From the game
Hit circleRadius 31 pixels: the line touches Rayquaza when it passes 31 pixels or less from the centre, in whole pixels. The centre moves with the animation and sits 13 pixels left and 40 up from the spot it stands on when facing left (3 pixels left and 40 up facing right). A centre more than 31 pixels off the screen never touches.Source 14: From the game
A touchBreaks the line, but costs energy only from a charging Pokemon or a line attacker like Steelix. Then it does nothing at all, and the line cannot mark it again. Only a frame's strongest hit counts; in the Fire, Rock and Flying reactions a touch leaves the line whole.Source 14: From the game, the rule Source 15: Read in code, which species attack by touch Source 16: From the game, what it does next
Leaves afterNever: it has no leaving timer.Source 12: From the game, value unconfirmedSource 17: Best reading (unconfirmed), seconds
Screen scaleOne game unit is 8 pixels (the field box is 32 by 24 units, the DS screen 256 by 192 pixels).unconfirmedSource 18: Best reading (unconfirmed)

How exact the field is

    Left out: the leaving countdown, herds, sounds and screen shake. Moves not decompiled yet are walked instead. Which background the game uses for each place is not decoded, so the field picks one.

    Browser entry

    Browser No. 210 · Rayquaza

    Rayquaza rampages while spitting energy.

    It is said to be impossible to capture.

    The game's own words, quoted exactly as the Browser shows them (US version). Source 4: From the game

    Where to find Rayquaza

    1. Fall City
    2. East Road
    3. Lyra Forest
    4. Krokka Tunnel
    5. Waterworks
    6. Safra Sea
    7. Olive Jungle
    8. Jungle Relic
    9. Kisara Plain
    10. Dusk Factory
    11. Panula Cave
    12. Sekra Range
    13. Go-Rock Base
    14. Fiore TempleBulbapedia

    Fiore's areas in order, a sketch rather than a map. The numbers count its placements in the map data across the story.

    The game's maps and spawn lists never place Rayquaza, so its data does not show where you meet it; what brings it in is not decoded yet. Source 3: From the game

    Bulbapedia's location pages list it (dashed on the sketch):

    Mission boss

    Bulbapedia's mission list names Rayquaza as the boss of The Temple's Sinister Shadows?. Mission scripts are not decoded yet, so this comes from Bulbapedia, not from the game's data.

    Capture data

    How these rules work for every Pokemon: How capture works and Capture EXP.

    WhatRayquazaSource
    Loops to capture13 (the capture check uses exactly this number)Source 19: Cross-checked
    Base capture EXP600Source 20: From the game
    Bonus for extra loopsUp to +395 in all: each loop past 13 adds a share of 399 from its row of the EXP table, rounded down loop by loop.Source 20: From the game
    Group bonus+300 with 2 Pokemon in the loop, +420 with 3, +600 with 4 or more.Source 20: From the game
    Styler damage per hit8 energy points (game value divided by 10)Source 21: From the game, value Source 14: From the game, the divide
    Size classLarge (game value 37; small is under 12, large 18 and up)Source 9: From the game

    Poke Assist

    Rayquaza gives a Flying assist that lasts 90 seconds. Source 2: Cross-checked Every Flying assist, longest first

    Never usable in play. Rayquaza's assist is in the data but never helps you: Bulbapedia's Poke Assist list marks it unusable, and The Cutting Room Floor lists it with the unused assists and field moves of Pokemon met only in Capture Challenges or story fights. Source 2: Cross-checked

    How Rayquaza reacts to Poke Assists

    What each assist does when it hits Rayquaza, measured by running the game's own reaction code on its data (what was measured). Frames are the game's, 60 to a second. Source 22: From the game

    How Rayquaza reacts to each Poke Assist
    AssistWhat happensOut of action
    WaterLifted in a bubble Source 23: Read in code, that the bubble's size reaches the hit65 frames (1.1 s)
    IceFrozen in place171 frames (2.9 s)
    FlyingBlown 22 px up97 frames (1.6 s)
    RockKnocked 10 to 21 px along268 frames (4.5 s)
    PsychicLifted 20 px and held until the Psychic friend has leftwhile held, then 227 frames (3.8 s)
    GhostSpins, circled by a ghostly shape91 frames (1.5 s)
    BugHeld in place, turning side to side161 frames (2.7 s)
    PoisonHeld in place, turning side to side101 frames (1.7 s)
    GroundHeld in place, turning side to side41 frames (0.7 s)
    GrassHeld in place, turning side to side11 frames (0.2 s)
    The two partner typesReacts to the partner's assist unconfirmedSource 24: Best reading (unconfirmed), which partner each type is151 frames (2.5 s) each

    Fire does nothing to it (a matchup of 0). Electric makes no Pokemon react, and Fighting counts loops instead. Source 22: From the game

    How assists react against each target, and why some show an arrow: How Poke Assists work.

    Field move

    Rayquaza has no field move, so it cannot clear obstacles.

    The Dragon group

    A Pokemon's group decides how Poke Assists affect it. All 6 Dragon-group Pokemon in the Browser:

    Sources

    Numbers come from the game's own data on a US copy of Pokemon Ranger (DS, 2006), and rules from a decompilation of its code, unless a sentence names another source. Nothing is copied from another wiki.

    A marker's shape shows how sure a fact is: From the game Read in code Cross-checked Best reading (unconfirmed). How this wiki is made

    1. Cross-checked. species-record.md: the 60-byte species record (loops to capture, capture EXP, size class, hop speed, turn speed); Pokemon_GetLoopsToCapture, Pokemon_GetCaptureExp, Pokemon_IsSizeSmall, Pokemon_GetTurnSpeed. Proven. Back to text
    2. Cross-checked. The game's own data tables, matched against Bulbapedia, Serebii and The Cutting Room Floor (checked 2026-10-16). Back to text: a b c d
    3. From the game. The game's own data tables, read from a US copy of Pokemon Ranger (DS, 2006) each time the wiki is built. Back to text: a b
    4. From the game. The game's own data tables on a US copy of Pokemon Ranger (DS, 2006), decoded for this wiki: the species table, the Browser, the map layers and spawn lists. Back to text: a b
    5. From the game. The Browser of a US copy of Pokemon Ranger: Shadows of Almia (DS, 2008): the number from the table the Browser reads by species (sub_0201DF54, read in code); group, Poke Assist, field move and level from the species-table columns it copies. A species with several data rows shows its lowest; which row the Browser picks is not traced. Back to text
    6. From the game. The Browser list of a US copy of Pokemon Ranger: Guardian Signs (DS, 2010): the number and its species row (func_02060AA8), and from that row the field move and level and the Poke Assist type and level (read by the target panel, the release scene and func_02041F84), all read in code. Back to text
    7. From the game. The capture field draws the game's own field sprites, animations and capture backgrounds, decoded from the game, played frame by frame with the game's own timing. Which background each place uses is the wiki's choice. Back to text
    8. From the game. movement-profile.md, move-geometry.md, locomotion-types.md, wander-target.md, fliers-effects.md, water.md: units, the two speeds, turning, where a Pokemon walks next, the field box and every mover; Pokemon_GetWalkSpeed, Angle_StepToward, Pokemon_ChooseWanderTarget, Pokemon_MoveDefault, Pokemon_MoveHover, Pokemon_MoveShootFlyer. Proven. Back to text: a b c d e
    9. From the game. Same as source 1. Back to text: a b
    10. Best reading (unconfirmed) (pixels). A value from the game's own data tables; what it means here is a reading, not yet confirmed. Back to text
    11. From the game. idle-turn-airborne.md: rest times, hovering, hops and gravity; Pokemon_RollRestTime, Pokemon_HandleRestGround, Pokemon_MoveHop. Proven. Back to text
    12. From the game. decide-and-timing.md, behaviour-subrecord.md: the action chance and type, the cooldown, the first decision; Pokemon_HandleState2, Pokemon_RollSpecialAction. Proven. How it starts (walk, rest or decide at once) is the first state, Pokemon_HandleState0, proven too. Back to text: a b c
    13. From the game (what the type does). attacks.md, water.md: the capture target's action table, its main attack and projectile, the charge, the field-wide attack, diving and surfacing; Pokemon_PickKind2Action, Pokemon_HandleState8, Pokemon_FireProjectile, Pokemon_HandleDive. Proven. Back to text
    14. From the game. hit-test.md and the findings' answers 68 and 69: the line against the Pokemon, a circle per species from record +0x04 to +0x07, the whole-pixel distance test, what a touch does; Pokemon_SetHitCircle, Capture_CheckPokemonHits, Line_CircleTouches, Pokemon_MarkLineTouched, Pokemon_HandleState5a. Proven; whether the touch reaction starts on the touch's own frame or the next is read in code. Back to text: a b c
    15. Read in code (which species attack by touch). line-break-damage.md: Styler damage per hit, line breaks, the energy gauge; Capture_BreakLine, StylerGauge_DecrementEnergy, proven. The pre-release review corrected when a touch costs energy: also for line attackers, not only during the charge; which species are line attackers is read in code. Back to text
    16. From the game (what it does next). touch.md and holdouts.md and the findings' answers 81, 82 and 90 to 97: what a touch sets off and the species that answer it with a move of their own, the first state, the timed row switch, the vine, Entei, Raikou, Suicune, Deoxys and Charizard; Pokemon_StartTouchReaction, Pokemon_TakeSpeciesState, Pokemon_HandleState0, Pokemon_TickSpeciesTimerRow, Pokemon_HandleVine. Proven, and the game's own code run under emulation answers a touch the same way for all 213 species. Charizard's landing, the move 14 species answer a touch with, and what starts Suicune's copies are not decompiled yet. Back to text
    17. Best reading (unconfirmed) (seconds). Same as source 10. Back to text
    18. Best reading (unconfirmed). Same as source 8. Back to text
    19. Cross-checked. capture-loop.md, capture-release.md, capture-state.md: crediting a loop, the two-ray inside test, the lift, letting go; Capture_CreditLoop, Capture_CreditDrawnLoop, Capture_ResolveLine. Proven; the release handler is read in code. Back to text
    20. From the game. exp-bonus.md: capture EXP, the group bonus and the loop bonus, Entei's row change; Pokemon_SetLoopCountAndExpBonus, Pokemon_GetCaptureExp. Proven. Back to text: a b c
    21. From the game (value). Same as source 15. Back to text
    22. From the game. content/ranger/assist-reactions.json: the game's own reaction code run under emulation for each of the 213 capture-field species (2026-10-29), every Poke Assist type's hit at 5 moments of the Pokemon's own behaviour. Each stored time matches the matchup formula on the species' own data, and the build checks that. Two steps rest on functions read in the code but not yet run: the one that passes a touching effect to the reaction (behind the Fire result) and the one that hands a released bubble's size to the Water hit. Back to text: a b
    23. Read in code (that the bubble's size reaches the hit). Same as source 22. Back to text
    24. Best reading (unconfirmed) (which partner each type is). Same as source 22. Back to text

    Notes on the sources

    • Bulbapedia's location pages, read from web.archive.org copies: Fiore Temple (archived 2026-08-23). What they say is theirs, retold in the wiki's words.
    • Mission bosses: Bulbapedia's mission list (archived 2026-01-07).

    Your cartridge says otherwise? File a field report.

    Every number here is read from the game, so the wiki is not crowd-edited. Each report is checked against the game's data and code. If you are right, the page is fixed, says what changed and why, and can thank you by name.

    File a field report

    Your Loopbook

    Read to the end and Rayquaza joins your Loopbook, the list of what you have read on this device.

    Rayquaza, Browser No. 210, is in your Loopbook.

    Open your Loopbook