Ranger Wiki · Unofficial

Staravia

From the Pokemon Ranger Wiki · Shadows of Almia (R-024) · Guardian Signs (R-229)

Staravia is in Shadows of Almia (R-024) and Guardian Signs (R-229). Its Poke Assist is Flying, and its field move is Cut 2 in Almia and Cut 3 in Guardian Signs. It is not in the first Pokemon Ranger, so this page has no capture field.

In Shadows of Almia, Staravia's capture gauge is 480; at Styler level 1 that is 48 loops, and at level 50, 3. Source 1: Read in code unconfirmedSource 2: Best reading (unconfirmed), fewest loops with no drain In Guardian Signs, Staravia's capture gauge is 1,904 and refills 50 a second once you stop looping; how many loops that takes is not decoded yet. Source 3: Read in code The hardest captures in all three games.

In the Ranger series

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

GameBrowser number
Pokemon Ranger (2006)Not in the Browser Source 7: From the game
Shadows of Almia (2008)R-024 Source 4: Cross-checked
Guardian Signs (2010)R-229 Source 6: Cross-checked

In Shadows of Almia

Pokemon Ranger: Shadows of Almia (DS, 2008), from the game's own data (US copy).

Staravia in Shadows of Almia: its stand animation at the game's own frame timing Source 8: From the game
Browser numberR-024 Source 4: Cross-checked unconfirmedSource 9: Best reading (unconfirmed), three-digit R- form
GroupFlying Source 5: Read in code
Poke AssistFlying Source 4: Cross-checked
Assist power10 at level 1, 24 at level 10, 205 at level 50 unconfirmedSource 10: Best reading (unconfirmed), by Styler level
Field moveCut 2 Source 4: Cross-checked
Capture gauge480 Source 1: Read in code
Styler EXP for a capture34 unconfirmedSource 11: Best reading (unconfirmed)

Browser entry

Shadows of Almia · R-024 · Staravia

It sends out twisters. It also rams to

attack.

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

Loops at your Styler level

The loops Staravia needs depend on your Styler level: each loop adds the Styler's capture power at its level Source 13: Read in code to Staravia's capture gauge of 480 Source 1: Read in code.

Each loop adds 10: 48 loops fill the gauge of 480.

The result uses the game's gain per loop Source 1: Read in code, formula; assist values by level unconfirmedSource 14: Best reading (unconfirmed), that the assist row is the Styler level; matchup factors Source 15: 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 2: Best reading (unconfirmed), fewest loops with no drain.

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

Where it is found

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

  • Peril Cliffs: 6 placements on 3 maps

In Guardian Signs

Pokemon Ranger: Guardian Signs (DS, 2010), from the game's own data (US copy). It has no groups: the Poke Assist type plays that part.

Staravia, its field sprite from Guardian Signs
Staravia in Guardian Signs: the first frame of its field movement set, a still Source 17: From the game
Browser numberR-229 Source 6: Cross-checked unconfirmedSource 18: Best reading (unconfirmed), three-digit R- form
Poke AssistFlying, level 3 Source 6: Cross-checked, type Source 19: Read in code, level
Field moveCut 3 Source 6: Cross-checked
Capture gauge1,904 Source 3: Read in code
Gauge refill50 a second (+5 every 6 frames), after a 3 second wait (180 frames) Source 3: Read in code
Styler EXP for a capture800 Source 20: Read in code

Browser entry

Guardian Signs · R-229 · Staravia

It launches twisters.

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

Capture gauge

No loop count yet: each loop carries the Styler's Power, 10 at level 1 and 327 at level 99, plus 5 for each Power Plus Source 22: Read in code, but how Power fills the gauge is not decoded.

Where it is found

The story maps never place Staravia; legendary, Sign and Ranger Net Pokemon come in by scripts not decoded yet Source 23: Read in code, the count.

A second set of maps, the multiplayer missions by a reading, places it 4 times unconfirmedSource 24: Best reading (unconfirmed), that the second set is multiplayer.

Sources

Numbers come from each game's own data on a US copy, and rules from each game's code as far as it has been read, unless a sentence names another source. Nothing is copied from another wiki; Serebii's lists were only compared.

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. 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
  2. Best reading (unconfirmed) (fewest loops with no drain). Same as source 1. Back to text: a b
  3. Read in code. The capture table: the gauge (func_ov003_020F1E60; the gauge shown is 100 times the current value over it), the refill amount, the wait before it starts and the frames between refills (func_ov003_020EFD88), all read in code. Back to text: a b c
  4. 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 e f
  5. 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: a b
  6. Cross-checked. Serebii's Guardian Signs Ranger Browser list, compared row by row with the US data on 2026-10-23: all 307 numbers and names agree. Serebii names five field moves differently from the US game (Slash, Break, Slam, Flame and Water for Cut, Crush, Tackle, Burn and Soak); once mapped, every field move agrees. Six Poke Assists and one field move level differ; there the wiki keeps the US value and says what Serebii lists. Back to text: a b c d e
  7. 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
  8. 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
  9. 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
  10. Best reading (unconfirmed) (by Styler level). 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
  11. 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
  12. From the game. The Browser description of a US copy of Pokemon Ranger: Shadows of Almia, quoted word for word. Back to text
  13. 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
  14. Best reading (unconfirmed) (that the assist row is the Styler level). Same as source 10. Back to text
  15. 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
  16. 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
  17. From the game. The field sprite, decoded from the game's own graphics: the first frame of its field movement set, a still. The game's animation files are not decoded yet, and which way that frame faces is not confirmed. Back to text
  18. Best reading (unconfirmed) (three-digit R- form). Serebii numbers the last six entries S-001 to S-006, and the US menu text holds both an R- and an S- prefix. The three-digit form follows Serebii's list; how the game pads the number on screen is not confirmed in its code yet. Back to text
  19. Read in code (level). 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
  20. Read in code. The capture table's EXP field, which CCapturePlayer__v14 adds to the capture's running total (read in code). That this total is what the result screen shows is not traced. Back to text
  21. From the game. The Browser description of a US copy of Pokemon Ranger: Guardian Signs, quoted word for word. Back to text
  22. Read in code. The Styler level table: Power at each level, plus 5 per Power Plus (func_0205D804, read in code). How Power, charge and Latent Power turn into gauge per loop is not decoded yet. Back to text
  23. Read in code (the count). Every map's Pokemon placement layer (2,549 placements), its fields named by a schema table the game's code reads. Story maps and the second set are told apart by where they load from; that the second set is the multiplayer missions is a reading. Which area each map belongs to is not decoded yet. Back to text
  24. Best reading (unconfirmed) (that the second set is multiplayer). Same as source 23. Back to text

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

Open your Loopbook