Hitmonlee
From the Pokemon Ranger Wiki · Guardian Signs (R-101)
Hitmonlee is in Guardian Signs (R-101). Its Poke Assist is Fighting, and its field move is Crush 3. It is not in the first Pokemon Ranger, so this page has no capture field.
In Guardian Signs, Hitmonlee's capture gauge is 3,360 and refills 90 a second once you stop looping; how many loops that takes is not decoded yet. Source 1: Read in code The hardest captures in all three games.
In the Ranger series
Hitmonlee is in the Browser of one of the three Ranger games.
| Game | Browser number |
|---|---|
| Pokemon Ranger (2006) | Not in the Browser Source 3: From the game |
| Shadows of Almia (2008) | Not in the Browser Source 4: From the game |
| Guardian Signs (2010) | R-101 Source 2: Cross-checked |
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.

| Browser number | R-101 Source 2: Cross-checked unconfirmedSource 6: Best reading (unconfirmed), three-digit R- form |
|---|---|
| Poke Assist | Fighting, level 4 Source 2: Cross-checked, type Source 7: Read in code, level |
| Field move | Crush 3 Source 2: Cross-checked |
| Capture gauge | 3,360 Source 1: Read in code |
| Gauge refill | 90 a second (+9 every 6 frames), after a 3 second wait (180 frames) Source 1: Read in code |
| Styler EXP for a capture | 2,400 Source 8: Read in code |
Browser entry
It creates shock waves
around itself that make Pokémon Paused.
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 10: Read in code, but how Power fills the gauge is not decoded.
Where it is found
The story maps place Hitmonlee 5 times on 5 maps Source 11: Read in code, the count. Which area each map belongs to is not decoded yet, so places are not named.
A second set of maps, the multiplayer missions by a reading, places it 4 times unconfirmedSource 12: 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
- 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 - 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 f
- 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
- 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 - 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
- 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
- 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 andfunc_02041F84), all read in code. Back to text - Read in code. The capture table's EXP field, which
CCapturePlayer__v14adds to the capture's running total (read in code). That this total is what the result screen shows is not traced. Back to text - From the game. The Browser description of a US copy of Pokemon Ranger: Guardian Signs, quoted word for word. Back to text
- 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 - 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
- Best reading (unconfirmed) (that the second set is multiplayer). Same as source 11. 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 reportYour Loopbook
Read to the end and this page joins your Loopbook, the list of what you have read on this device.
Open your Loopbook