Ranger Wiki · Unofficial

Ninjask

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

Ninjask takes 1 loop 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 is Flying, and it has no field move. It is also in Shadows of Almia.

In Pokemon Ranger, Ninjask takes 1 loop at any Styler level, and 207 Pokemon in that game take more. Source 1: Cross-checked In Shadows of Almia, Ninjask's capture gauge is 490; at Styler level 1 that is 49 loops, and at level 50, 3. Source 2: Read in code unconfirmedSource 3: Best reading (unconfirmed), fewest loops with no drain The hardest captures in all three games.

In the Ranger series

Ninjask is in the Browser of two of the three Ranger games.

GameBrowser number
Pokemon Ranger (2006)No. 032 Source 6: From the game
Shadows of Almia (2008)R-180 Source 7: Cross-checked
Guardian Signs (2010)Not in the Browser Source 8: From the game

Pokemon Ranger (DS, 2006): the sections down to Shadows of Almia cover this game.

How Ninjask moves

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

WhatNinjaskSource
MovementFlies and never lands; when it starts a walk it may pick a new height; it can shoot while flying (movement type 24).Source 10: From the game
Turn speedUp to about 2.1 degrees a frame, always the short way round (game value 150).Source 11: From the game
Walk speedAbout 6.00 pixels a frame (game value 3,072).Source 10: From the game, value unconfirmedSource 12: Best reading (unconfirmed), pixels
Run speedGame value 3,584 a frame, for fast walks and some special actions.Source 10: From the game
Where it walks nextA random spot 50 to 50 pixels away, inside field area 0 (x 32 to 223, y 61 to 169); it tries up to 8 times, then takes the last.Source 10: From the game
RestsNever (its rest time is 0, with no random extra)Source 13: From the game
TurningTurns while it walks; stops to turn only near its stop, when 45 degrees or more off course.Source 10: From the game
Flying height16 pixels plus up to 7 more, picked for each flight.Source 10: From the game unconfirmedSource 14: Best reading (unconfirmed), pixels
Special actionNo special action.Source 15: From the game, chance and type Source 16: From the game, what the type does
At the startDecides on its first frame, with its usual chance.Source 15: From the game
Hit circleRadius 8 pixels: the line touches Ninjask when it passes 8 pixels or less from the centre, in whole pixels. The centre moves with the animation and sits 13 pixels left and 12 up from the spot it stands on when facing left (3 pixels left and 12 up facing right). A centre more than 8 pixels off the screen never touches.Source 17: From the game
A touchBreaks the line, but costs energy only from a charging Pokemon or a line attacker like Steelix. Then it spins two whole turns in about half a second (31 frames), then decides again. Only a frame's strongest hit counts; in the Fire, Rock and Flying reactions a touch leaves the line whole.Source 17: From the game, the rule Source 18: Read in code, which species attack by touch Source 19: From the game, what it does next
Leaves after40 seconds (a countdown of 30, which the code turns into 2,400 frames). Not simulated here.Source 15: From the game, value unconfirmedSource 20: 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 21: 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. 032 · Ninjask

    Ninjask darts around at dazzling speed

    while furiously flapping its wings.

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

    Where to find Ninjask

    1. Fall City
    2. East Road
    3. Lyra ForestBulbapedia
    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 Temple

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

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

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

    • Lyra Forest: on its list of wild Pokemon after the credits; hiding in Big Trees, by its obstacle table (its Lyra Forest page)

    Capture Arena

    • Round 8: one of the wild Pokemon (spawn weight 5 of the round's 115), worth 4,200 points

    Round numbers, the roles (wild Pokemon, recharge helper, boss) and the points are a reading of the Arena's spawn data; how a spawn weight becomes odds is not decoded yet. unconfirmedSource 22: Best reading (unconfirmed)

    Capture data

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

    WhatNinjaskSource
    Loops to capture1 (the capture check uses exactly this number)Source 23: Cross-checked
    Base capture EXP60Source 24: From the game
    Bonus for extra loopsUp to +14 in all: each loop past 1 adds a share of 16 from its row of the EXP table, rounded down loop by loop.Source 24: From the game
    Group bonus+30 with 2 Pokemon in the loop, +42 with 3, +60 with 4 or more.Source 24: From the game
    Styler damage per hit2 energy points (game value divided by 10)Source 25: From the game, value Source 17: From the game, the divide
    Size classSmall (game value 11; small is under 12, large 18 and up)Source 11: From the game

    Poke Assist

    Ninjask gives a Flying assist that lasts 30 seconds. Source 4: Cross-checked Every Flying assist, longest first

    How Ninjask reacts to Poke Assists

    What each assist does when it hits Ninjask, 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 26: From the game

    How Ninjask reacts to each Poke Assist
    AssistWhat happensOut of action
    FireTurns away and hops 40 to 47 px up Source 27: Read in code, that every Fire hit gives this short reaction20 frames (0.3 s)
    WaterLifted in a bubble Source 27: Read in code, that the bubble's size reaches the hit247 to 248 frames (4.1 s)
    FlyingBlown 77 to 99 px up198 to 211 frames (3.3 to 3.5 s)
    RockKnocked 10 to 35 px along248 to 253 frames (4.1 to 4.2 s)
    PsychicLifted 20 to 23 px and held until the Psychic friend has leftwhile held, then 207 to 208 frames (3.5 s)
    GhostSpins, circled by a ghostly shape181 frames (3 s)
    BugHeld in place, turning side to side161 frames (2.7 s)
    PoisonHeld in place, turning side to side151 frames (2.5 s)
    The two partner typesReacts to the partner's assist unconfirmedSource 28: Best reading (unconfirmed), which partner each type is201 frames (3.4 s) and 321 frames (5.3 s)

    Ice, Ground and Grass never reach it: they only reach a Pokemon on the ground, and Ninjask floats or flies. Electric makes no Pokemon react, and Fighting counts loops instead. Source 26: From the game

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

    Field move

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

    The Bug group

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

    In Shadows of Almia

    Pokemon Ranger: Shadows of Almia (DS, 2008), from the game's own data (US copy). The Pokemon Ranger numbers above do not apply here.

    Ninjask, its field sprite from Shadows of Almia
    Ninjask in Shadows of Almia: the first frame of its stand set Source 29: From the game
    Browser numberR-180 Source 7: Cross-checked unconfirmedSource 30: Best reading (unconfirmed), three-digit R- form
    GroupBug Source 31: Read in code
    Poke AssistBug Source 7: Cross-checked
    Assist powerThree stored values: 5, 10, 20 at level 1, 103, 205, 410 at level 50 unconfirmedSource 32: Best reading (unconfirmed), what each of the three does
    Field moveCut 2 Source 7: Cross-checked
    Capture gauge490 Source 2: Read in code
    Styler EXP for a capture100 unconfirmedSource 33: Best reading (unconfirmed)

    Browser entry

    Shadows of Almia · R-180 · Ninjask

    It flies around at blinding speed.

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

    Loops at your Styler level

    The loops Ninjask needs depend on your Styler level: each loop adds the Styler's capture power at its level Source 35: Read in code to Ninjask's capture gauge of 490 Source 2: Read in code.

    Each loop adds 10: 49 loops fill the gauge of 490.

    The result uses the game's gain per loop Source 2: Read in code, formula; assist values by level unconfirmedSource 36: Best reading (unconfirmed), that the assist row is the Styler level; matchup factors Source 37: Read in code. It is a minimum, for uncharged loops with no drain and no other bonus: the gauge drains over time at a rate not found yet, and two bonuses of half the capture power depend on conditions not traced unconfirmedSource 3: Best reading (unconfirmed), fewest loops with no drain.

    Loops with no assist and no Power-up Data
    Styler levelCapture powerLoops
    11049
    102421
    205210
    301005
    401554
    502053

    Where it is found

    The game's maps place Ninjask in these areas unconfirmedSource 38: Best reading (unconfirmed), area names. Some spots may depend on story progress, which the map data does not record.

    • Chroma Road: 1 placement on 1 map

    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. Read in code. The battle species table's capture gauge column, which sets up the target's gauge (CBattleEnemyGauge). Gain per loop (ov1_0212CD6C): the Styler's capture power times a charge factor of 1, 2 or 3, plus the Normal, Fire or Fighting assist's value (minus the Dark assist's), times the matchup factor for those four assists, plus Power-up Data (3, 5 or 7). Both read in code. Back to text: a b c d
    3. Best reading (unconfirmed) (fewest loops with no drain). Same as source 2. Back to text: a b
    4. 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
    5. 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
    6. 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
    7. Cross-checked. Serebii's Shadows of Almia Ranger Browser list, compared row by row with the US data on 2026-10-23: all 267 numbers, names and Poke Assists agree. Field move or level differs in 8 cells; there the wiki keeps the US value and says what Serebii lists. Back to text: a b c d
    8. 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
    9. 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
    10. 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 f
    11. From the game. Same as source 1. Back to text: a b
    12. 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
    13. From the game. idle-turn-airborne.md: rest times, hovering, hops and gravity; Pokemon_RollRestTime, Pokemon_HandleRestGround, Pokemon_MoveHop. Proven. Back to text
    14. Best reading (unconfirmed) (pixels). Same as source 12. Back to text
    15. 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
    16. 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
    17. 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
    18. 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
    19. 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
    20. Best reading (unconfirmed) (seconds). Same as source 12. Back to text
    21. Best reading (unconfirmed). Same as source 10. Back to text
    22. Best reading (unconfirmed). Same as source 12. Back to text
    23. 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
    24. 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
    25. From the game (value). Same as source 18. Back to text
    26. 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
    27. Read in code (that every Fire hit gives this short reaction; that the bubble's size reaches the hit). Same as source 26. Back to text: a b
    28. Best reading (unconfirmed) (which partner each type is). Same as source 26. Back to text
    29. From the game. The field sprite, decoded from the game's graphics: the first sequence of its stand set, at the game's own frame timing when that sequence is plain frames, a still when it carries motion commands not decoded yet. Which way it faces is not confirmed. Back to text
    30. Best reading (unconfirmed) (three-digit R- form). Stored as a plain number; the US menu text has only an R- prefix for it. The three-digit form follows Serebii's list; how the game pads it on screen is not confirmed in its code yet. Dialga, Palkia and Shaymin are stored after the list as 1001 to 1003, for the special missions; how the game numbers them on screen is not found yet. Back to text
    31. Read in code. 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
    32. Best reading (unconfirmed) (what each of the three does). The assist power table (one row per level, one value or three per assist type), read through its accessor in code. That its row is the Styler level is a reading, not confirmed, and what the three values of Water, Ice, Bug, Dragon and Steel do is not decoded. Back to text
    33. Best reading (unconfirmed). The capture EXP column of the battle species table. Its values only make sense as Styler EXP (10 for early Pokemon, thousands for legendaries, on the same scale as the Styler's EXP table), but the code that pays it out is not traced. Back to text
    34. From the game. The Browser description of a US copy of Pokemon Ranger: Shadows of Almia, quoted word for word. Back to text
    35. Read in code. The Styler level table (levels 1 to 50: energy, capture power and EXP), read through its accessors in code; the capture loop asks it for the capture power at the current Styler level. Back to text
    36. Best reading (unconfirmed) (that the assist row is the Styler level). Same as source 32. Back to text
    37. Read in code. The assist matchup chart in the capture code (1.5 strong, 0.75 weak, no immunities), read in code; the in-game glossary's lists of weak matchups agree with its 0.75 cells. Back to text
    38. Best reading (unconfirmed) (area names). Each map's Pokemon layer (1,139 placements on 271 maps in 35 areas). Area names come from the game's place-name list by area number, checked against each area's own text for about 15 areas and against the habitats. The layers store no story phase, and Pokemon brought in by story or mission scripts are not in them. Back to text

    Notes on the sources

    • Bulbapedia's location pages, read from web.archive.org copies: Lyra Forest (archived 2026-07-24). What they say is theirs, retold in the wiki's words.

    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 Ninjask joins your Loopbook, the list of what you have read on this device.

    Ninjask, Browser No. 032, is in your Loopbook.

    Open your Loopbook