Skip to calculator

Let's Go Damage Calculator for Pikachu & Eevee

Use the Let's Go damage calculator to test attacks in Pokémon: Let's Go, Pikachu! and Let's Go, Eevee! Set the rules, choose both Pokémon and compare the move results.


Pokémon 1's Moves (select one to show detailed results)
??? - ???%
??? - ???%
??? - ???%
??? - ???%
Pokémon 2's Moves (select one to show detailed results)
??? - ???%
??? - ???%
??? - ???%
??? - ???%
Loading...
(If you see this message for more than a few seconds, try enabling JavaScript. If you have that enabled, try deleting your cookies. Otherwise, I won't be able to help you unless you send a screenshot of your browser console [Ctrl+Shift+I on Google Chrome].)

Pokémon 1

  
Custom sets only
BaseIVsAVs
341
236
236
236
236
236
236236
/341 (%)

Field
Auto-Level to:



                    
            


Please enter your custom set here.

Spread Name:



Pokémon 2

  
Custom sets only
BaseIVsAVsDVs
341
236
236
236
236
236
236236
/341 (%)

How to use the Let's Go damage calculator

This page is for the Let’s Go games, not Pokémon GO or a main-series VGC ruleset. The familiar two-panel layout does not mean that all games use identical stat inputs. Before testing a matchup, decide which battle rules you want to model. A story battle with trained awakening values is a different scenario from a restricted competitive battle that ignores them.

Select a Pokémon or preset on each side, check its form and level, and choose a move in the attacker’s panel. Set the defender’s HP and defensive stats, then review friendship, nature and the selected field conditions. The tool recalculates when inputs change. Use the move-result selector to see the detailed output for that attack, and repeat the same setup on the other side to compare return damage.

Understand AVs before comparing stats

Awakening values, often called AVs or Go Power, increase stats in Let’s Go through its Candy and leveling systems. They are not the EV system used in many other Pokémon games. When the active rules permit AVs, a trained Pokémon can have very different final stats from an otherwise identical untrained one. Entering familiar EV numbers without checking the labels will not reproduce that difference accurately.

The Let’s Go damage calculator exposes the relevant inputs so you can test the intended rules rather than borrowing a main-series spread. Under Normal Rules, awakening values are ignored by the battle format. Check the rules control before deciding whether an AV adjustment should change the result. If you are modeling another format, verify its restrictions rather than assuming every opponent has the same training.

Set friendship, nature and the battle level

Friendship is another reason a Let’s Go matchup can differ from a standard damage comparison. This page provides a friendship input for each Pokémon. Its Normal Rules handling uses the format’s configured friendship value of 70, so a custom value may not apply in the same way under every setting. First identify the rules, then confirm the resulting stats in the panel.

Level, IVs and nature also contribute to the final numbers. Enter the battle level you intend to use, and inspect the Auto-Level control if the two panels do not reflect the values you expected. A nature can strengthen one stat while weakening another. Change friendship or nature independently of the move so you can see whether the relevant offensive or defensive stat actually moved.

SettingWhy it mattersWhat to check
Battle rulesDetermine whether AVs affect the matchupNormal Rules versus the intended alternative
FriendshipCan affect applicable final statsEach panel and the selected rules
IVs and natureInfluence offense, defense and SpeedFinal stat values rather than labels alone
Level and HPChange the survival thresholdAuto-Level and current HP settings

Try a reproducible Rock Slide comparison

A blank preset can open with no move selected and show zero damage. That is an empty attack choice, not a claim that the species cannot deal damage. For a practical example, load Aerodactyl on both sides, select Rock Slide for the left Pokémon, and confirm equal levels and the intended rules. Record the displayed damage range before modifying any other value.

Now increase the attacker’s Attack input while leaving the defender unchanged. Compare the new final Attack and the Rock Slide range. Restore the attacker, then increase the defender’s Defense to see the opposite effect. The Let’s Go damage calculator makes this controlled comparison more useful than copying a single percentage from another player whose friendship, AVs or levels may differ.

Interpret percentages and knockout language

The output expresses damage as a range because the calculation allows different damage rolls. Its percentage is relative to maximum HP, while the current-HP input describes how much health remains before the attack. These are different reference points. A range below 100% can knock out a damaged target, whereas a high roll above 100% does not necessarily make every roll a knockout.

Use the detailed result to distinguish possible and guaranteed outcomes under the modeled conditions. A damage range does not include every decision in a battle: a move may miss, the opponent may switch, and the attacker may not act first. Compare realistic cases, including a target that has already taken chip damage, rather than treating one clean full-health matchup as the whole battle.

Check the field and troubleshoot mismatches

Use only the field controls relevant to the Let’s Go matchup. Reflect, Light Screen, Helping Hand and the available side effects can change an otherwise identical comparison. A physical move and a special move use different offensive and defensive stats, so adjusting the wrong defense may do nothing. Read the move’s displayed category before deciding which investment to test.

If the Let’s Go damage calculator disagrees with your expected result, work through the setup in a fixed order: game, rules, forms, levels, friendship, AV handling, move category and field effects. Confirm that a preset did not restore a value you had edited manually. Change one variable at a time and keep the result description alongside the input values so that the comparison can be reproduced.

Keep useful comparisons without losing your sets

Use the existing custom-set and export controls to retain a useful matchup. Browser-saved sets depend on local storage, so keep an exported copy before clearing site data or moving to another device. The same species in two exported files may have different rules assumptions; include enough context in your own notes to distinguish them.

This is a single-matchup aid rather than a complete simulation of the games. It does not choose an opponent’s move or guarantee a win. For another game, select the appropriate linked calculator instead of forcing unrelated abilities, items or generation mechanics into this page. Calculations run in the browser, while external assets may still make network requests; the privacy page explains that distinction.

Let's Go damage calculator questions

Is this a Pokémon GO damage calculator?

No. This tool is for the Nintendo Switch games Let’s Go, Pikachu! and Let’s Go, Eevee! Pokémon GO has different battle systems and is not modeled by this page. Match the game and battle rules before interpreting the output.

Why do my AV changes seem to have no effect?

Check whether Normal Rules is selected. That format ignores awakening values, so changing AV inputs may not change the battle stats used in the result. To investigate a different scenario, select its rules deliberately and confirm the final values in both panels.

Why is the initial damage zero?

Some blank presets start with No Move in their move slots. Open a move selector and choose a damaging move such as Rock Slide, then inspect the updated range. A status move or an immunity can also produce no direct damage; check the actual matchup.

Can I compare different friendship values?

The friendship fields let you inspect applicable scenarios, but battle rules can normalize the value. Check both the displayed friendship and the active rules before comparing results. Do not infer a rules change merely because a text field accepts a different number.