Viridian ForestPikachuExample encounter record
AliveFree browser Nuzlocke tool
Pokemon Nuzlocke Tracker for Route Logs and Team Status
Keep your run honest with a simple Pokemon Nuzlocke tracker. Record the area, first encounter, current status, notes, badge progress, game, and rule set in one local browser workspace. No account, spreadsheet, or server upload is required.
A clear run at a glance
50records
4statuses
8badges
Log encounters, mark losses, and keep route decisions visible before memory changes the story.
Run setup
Set up your Nuzlocke run
Add a run name, choose the game and rule style, then save each encounter as it happens. The example record shows the output format before you enter your own route.
Route logAdd an encounter
Your run is saved in this browser with local storage. It is not uploaded to Pokemon Roulette.
Run dashboard
0%Your encounter record
Encounters1
Active1
Fallen0
Badges0
Saved locally
1Encounter list
How it works
How to use this Pokemon Nuzlocke tracker
A route log is most useful when it takes seconds to update. Set the rules once, record the first legal encounter, and change the status as the run develops.
Name the run
Choose a short name and select the game or randomizer style. This keeps several challenge runs easy to distinguish when you copy a summary.
Record the first encounter
Enter the named area and the Pokemon you caught, attempted to catch, or lost. Add a note for a duplicate clause, gift, static encounter, or nickname.
Update the status
Use Alive while the Pokemon can battle, Boxed when it is stored, Fallen after a faint, and Released when your rules remove it from the run.
Save or share a checkpoint
Save run details after badge progress changes, then copy the summary for a stream description, group chat, personal backup, or post-run review.
Tracking guide
What makes a useful Nuzlocke encounter log?
The tracker is deliberately small: it captures the facts you need to make a run repeatable and fair without pretending to replace a complete spreadsheet or game-specific database.
Use the game's named areas
Write the area name exactly as you understand it before the encounter. This matters in caves, multi-floor routes, Wild Areas, Safari Zones, dens, and games with open-zone labels.
- Decide whether floors share one encounter limit.
- Use notes for areas with ambiguous boundaries.
- Keep your wording consistent across the run.
Separate the encounter from the outcome
A legal encounter can be caught, missed, duplicated, gifted, or lost. Record the Pokemon and explain the outcome rather than deleting the area when the result feels bad.
- Mark a missed catch in the note if your rules count it.
- Record a duplicate skip before choosing the replacement.
- Keep shiny or gift exceptions visible.
Treat status as a timeline
A Pokemon may move from Alive to Boxed, then to Fallen or Released. The list keeps the latest status visible, while notes preserve the reason for a special decision.
- Box temporary reserves instead of removing them.
- Mark a faint immediately after the battle.
- Use a note when a clause changes the normal flow.
Use the record as a decision aid
A route log helps you review team balance, badge progress, and recurring risks before the next major battle. It is a memory aid, not a promise that a run is automatically legal.
- Compare active members with your next level cap.
- Review fallen members before repeating a route.
- Use the Team Planner for type coverage questions.
Fair-play notes
Keep the rules visible before the result is emotional
A tracker cannot decide your Nuzlocke rules for you. Before the first route, write down whether the first encounter means the first battle, the first Pokemon seen, or the first catch attempt. Decide how duplicate species, gifts, static Pokemon, eggs, fishing spots, and shiny encounters work in your chosen game.
Use status labels consistently. Boxed does not mean dead: it is a legal reserve that may return later. Fallen should mean that the Pokemon fainted under the rule set you chose. Released is useful for a deliberate clause, trade, or self-imposed restriction, but your note should explain the decision so a future review is understandable.
For hardcore, Soul Link, randomizer, or ROM-hack runs, add the specific rule in the run name or a note. Level caps, set mode, item limits, linked deaths, altered encounters, and custom species pools can change what a record means. The tool stores your wording; you remain responsible for checking the game and community rules.
- Write area and fainting clauses before the first encounter.
- Do not delete an uncomfortable result just to make the log look cleaner.
- Use notes for gifts, static encounters, duplicate skips, and randomizer changes.
- Back up a copied summary if the run matters to a group or stream.
Boundaries and recovery
Common tracker edge cases
A good Pokemon Nuzlocke tracker should remain useful when the run is messy. These limits make the behavior predictable instead of silently changing your data.
Ambiguous areas
If a cave floor, den, gift room, or open-zone subarea is unclear, choose a naming rule before the encounter. Put the decision in the note so a future version of the run has context.
Fainted Pokemon
Changing a record to Fallen keeps the encounter in the history and updates the active count. The page does not erase a Pokemon because a death is part of the route story.
Reset and restore
Restore example brings back a safe sample record. Clear run removes the current records after confirmation, while local storage lets the browser remember the saved state between visits.
Record limit
The tool accepts up to 50 encounter records. That is enough for a normal run log; copy a summary and start a second checkpoint if a long randomizer exceeds the limit.
Questions
Pokemon Nuzlocke Tracker FAQ
What does a Pokemon Nuzlocke tracker record?
It records the run name, game and rule style, badge progress, area, encountered Pokemon, current status, and optional notes. Those fields cover the core facts most players need for a route log.
Does this tracker know whether an encounter is legal?
No. Legality depends on your game, area definitions, clauses, randomizer settings, and personal rule sheet. Use the note field to document the decision and read the rules before starting.
What is the difference between Boxed and Fallen?
Boxed means the Pokemon is still legal but not currently in the party. Fallen means it fainted under your rules and should no longer be used unless your written rule set explicitly says otherwise.
Can I use this for a hardcore Nuzlocke or randomizer?
Yes. Choose the closest game and rule style, then write level caps, item limits, altered encounters, or other special rules in the run name and notes. The tracker is a neutral log, not a rules engine.
Where is my Nuzlocke data stored?
The page uses local storage in the browser you are using. It does not upload the run to a server. Clearing browser data, switching browsers, or using private browsing can remove or isolate the saved state, so copy important summaries.
Can I track more than one Nuzlocke run?
The current local workspace is designed for one active run at a time. Copy a summary before clearing it, then start a new run with a different name. For many simultaneous runs, keep exported summaries in a separate note or spreadsheet.