MissingNo., the famous glitch Pokemon
The Glitchhouse · Pokemon Red, Blue and Yellow

MissingNo.: what it is, how to find it and what it does

The sprite: my own MissingNo., captured on a Super Game Boy

MissingNo. is a glitch Pokemon in Pokemon Red and Blue. It is what the game shows when it reaches one of the 39 empty places in its list of 190 species numbers: no real Pokemon lives there, so the game reads its stats and its picture from data that was never meant to be a Pokemon, and gets a broken block of pixels with 136 Attack and 0 Defense.

You meet it with the old man glitch: let the old man in Viridian City show you how to catch a Pokemon, fly to Cinnabar Island and surf along its east shore, where the letters of your name become the wild Pokemon. Meeting it adds 128 to the sixth item in your bag (when that stack holds fewer than 128) and scrambles part of the Hall of Fame record. Your saved game, the part that holds your team, your bag and your progress, is never touched.

Index numbers
39: 36 draw the block, 0xB6, 0xB7 and 0xB8 wear two fossils and a ghost
Pokedex number
000
Type
Bird / Normal
Base stats
33 HP, 136 Attack, 0 Defense, 29 Speed, 6 Special
Moves
Water Gun, Water Gun, Sky Attack
Where
Route 20's shore beside Cinnabar Island, after the old man
Your bag
sixth item +128, if under 128
Your save
untouched; the Hall of Fame record is not
In Yellow
no old man route; 182 to 184 battle, the other 36 depend on your save

Every fact here was tested in the game's own code in an emulator or read from its disassembly (pret), for the US Pokemon Red, Blue and Yellow, checked 2026-11-11.

The short version

What is MissingNo.?

Every Pokemon in Red and Blue has two numbers. Its Pokedex number runs from 1, Bulbasaur, to 151, Mew. Its index number, the one the game uses inside its code, runs from 1 to 190 in a different order: Rhydon is 1, Kangaskhan is 2. A list with 190 places for 151 Pokemon leaves 39 places empty. Each empty place still has a line in the game's tables: the name MISSINGNO., a cry, and the Pokedex number 0, which means none.

Ask the game for one of those 39 places, through the old man glitch, the Ditto glitch or a few rarer tricks, and MissingNo. is what you get: it is not a single creature but an empty slot, and thirty nine different empty slots all lead to it. The name is the developers' placeholder. Everything else about it, its stats, its types, its moves and its picture, is read from wherever the game's arithmetic happens to land.

1F203234383D3E3F4344454F505156575E5F73797A7F8687898C929C9FA0A1A2ACAEAFB5B6B7B8

The 39 index numbers, in hex. 36 of them are the same creature; the last three wear real pictures, below.

Every MissingNo. sprite

MissingNo. has four front sprites in Pokemon Red and Blue. 36 of its 39 index numbers draw the same broken block, unpacked from ROM address 0x1900. The other three wear real pictures the game keeps for other scenes: the Kabutops fossil (index 0xB6), the Aerodactyl fossil (index 0xB7) and the Lavender Tower ghost (index 0xB8).

MissingNo. front sprite, the block, in Game Boy grays
The block36 of the 39 slots, from index 0x1F on. How it gets built
MissingNo Ghost form
The ghostIndex 0xB8, the Lavender Tower spirit. Its own page
MissingNo Fossil Kabutops form
Kabutops fossilIndex 0xB6, the museum skeleton. Its own page
MissingNo Fossil Aerodactyl form
Aerodactyl fossilIndex 0xB7, the biggest body any MissingNo. can wear. Its own page

All four are front pictures from the Pokemon Red ROM, in the game's four shades and at their true sizes. The Aerodactyl fossil is 7 by 7 tiles, the ghost and the Kabutops fossil 6 by 6, and the block is shown in the full 7 by 7 battle frame, where it lands on the right. 'M (index 0x00) wears the block too. Yellow builds its own MissingNo. picture from different data (see across five cartridges), and the back picture, the one you see when you send it out, is read from video memory, so it has no single form. How the block gets built is shown further down.

The real mechanism, from the code

Why MissingNo. exists: 0 minus 1 is 255

The game keeps base stats in a table ordered by Pokedex number, and finds a Pokemon's row by taking its Pokedex number minus 1. For MissingNo. that sum is 0 minus 1. The Game Boy does it in a single byte, where 0 minus 1 wraps around to 255, so the game reads row 255 of a table that only has 150 rows (Mew's row is kept somewhere else). Row 255 lands in the middle of the trainer data, on the teams of the Bikers on Route 17 and the two listed after them. MissingNo.'s 28 bytes of stats are those Bikers' levels and Pokemon, read as if they were a Pokemon.

Decoder The 28 bytes the game reads for MissingNo., from the Red ROM (file offset 0x39FC2)

Tap a byte to see both meanings.

So MissingNo.'s 136 Attack is a Biker's Muk, which is index 136. Its Bird type is a Voltorb: Voltorb is index 6, and type number 6 is Bird, a type cut from every real Pokemon. Its two Water Guns are two Koffing, because Koffing's index, 55, is also Water Gun's move number, and its Sky Attack is a Weezing for the same reason. Even the picture follows the bytes: they point at ROM address 0x1900, which is not a picture at all but the middle of the game's own program code, the routine that copies the screen's tiles to video memory.

Read from the Red ROM and checked against pret's disassembly (data/trainers/parties.asm, which notes the same overlap); Blue's bytes are identical. The game's own header loader, run in an emulator, returns these same values for every one of the 36 look-alike index numbers.

Step by step

How to find MissingNo. in Red and Blue

The classic way is the old man glitch. You need a Pokemon that can use FLY and one that can use SURF.

  1. Pick your sixth item. If you want the famous item trick, put the item you want more of in the sixth place of your bag. You need at least six kinds of item for it to work.
  2. Watch the old man. In Viridian City, once you have the Pokedex, talk to the old man. Answer NO when he asks if you are in a hurry, and watch him catch the Weedle.
  3. Fly to Cinnabar Island. Do not set foot anywhere with wild Pokemon on land on the way: a route with grass, a cave or a forest replaces the list your name is sitting in. Towns and the sea are safe. Skip in-game trades and the Cable Club too; they use the same memory.
  4. Surf from the east edge. Walk to the east edge of Cinnabar, face the water and use SURF. You are now in the column of shore squares right next to the island. It belongs to Route 20, not to Cinnabar.
  5. Surf up and down that column. Wild Pokemon appear from your name. Your name fills the first five of the ten encounter slots; the other five are left over from the last place with wild Pokemon on land that you visited before the old man.
  6. Run, or catch it. The item change happens the moment the battle starts. Save afterwards to keep it.

Tested 2026-10-30 by playing it in the game's own code: a new game named ASH, the old man, then surfing Route 20's shore column right next to Cinnabar, in Red and Blue. The name brought 'M at levels 0 and 80 and a MissingNo. (index 135) at level 146. That column belongs to Route 20, not to Cinnabar: Cinnabar's own map gives no wild encounters at all.

Meet it in the battler: surf the coast as ASH, and slot 1 is this MissingNo. at level 146, to fight, run from or catch.

The other way in: the Ditto glitch

Escape from a trainer who has spotted you by flying away, then let a wild Ditto transform into one of your Pokemon. When you come back, the battle the game was waiting to start becomes the species whose index number matches that Pokemon's Special stat, at level 7. Give it a Special of 31, or any other MissingNo. index number, and you get a MissingNo. The full recipe is on the Ditto glitch page. In Red and Blue all 39 index numbers start a normal battle this way.

What differs in Pokemon Yellow

  • The old man's coast is closed. After the demo, 1,500 steps of surfing Route 20's shore column in Yellow gave no encounter at all.
  • The Ditto glitch reaches all 39. Index numbers 182, 183 and 184 (0xB6 to 0xB8, the fossil and ghost forms) always give a normal battle you can run from, so a Special of 182, 183 or 184 (or 438, 439 or 440) is the sure way.
  • The other 36 battle or freeze, and your cartridge decides. They all set the item bit. Then the game either goes on to the battle or locks up, and mostly it is bytes of your cartridge's save memory that decide, not the number you pick. In most saves I tested the 36 battled or froze together; in one save where 32 of them battled, 69, 79, 127 and 181 did not. In the four save memories I built (blank, erased to $FF the way the game's own erase does it, with 12 Hall of Fame teams and with 50) they all froze. Changing one unused byte of that memory, one that the game itself never writes (only overflowing glitch pictures do), can set the sound byte (below) to any value, and 48 of its 256 values made the very same battle reach its menu.
  • Why. All 36 read the picture of Pokedex number 0, and in Yellow that entry's picture address is $0006, the very start of the cartridge, where there is no picture. The game unpacks whatever bytes are there anyway: about 630 frames of black screen, about 10.5 seconds, writing past the picture buffers, through the Hall of Fame record and on into the game's own working memory, up to $C30F. One of the bytes it overwrites, at $C0EF, tells the sound code which part of the cartridge holds the music. Its new value is a mix of the picture's bits and of save memory bytes the game never clears: old Hall of Fame records, the unused bytes after them, and the leftovers of earlier MissingNo. pictures. Then MissingNo. cries, and the sound code jumps to address $6BD4 in whatever part of the cartridge that byte names. If that is a real sound routine, or code that happens to come back harmlessly, the battle goes on. If it is anything else, the game freezes. In a save with a blank Hall of Fame it lands inside the routine that teaches moves, so "MISSINGNO. learned" prints over and over for about a minute, then "MISSINGNO. is trying to learn", and pressing A there freezes the game.
  • How often it works. The sound byte can hold 256 values. In my test save, with index 67, 48 of them gave a battle with its menu, 166 froze the game with the screen gone blank or stuck, and 42 stopped the processor outright. In another save only 7 values worked, the ones that point at a real sound routine, because the code the other values run also reads the rest of the overwritten memory. Which value your cartridge gets depends on what its save memory holds, and every MissingNo. battle rewrites those bytes, so the next try can come out differently.
  • Your save is safe either way. The picture writes only to the part of the save memory that holds the Hall of Fame and the picture buffers. After a freeze, the saved game itself loaded normally in every test.

Tested 2026-11-14 in the game's own code in an emulator with no debugging hooks: all 39 index numbers in four save memories (the blank one as a Game Boy and as a Game Boy Color), and every value of the sound byte for index 67 (the first 96 run one by one, the other 160 following the same cartridge rule, checked on 6 of them). Earlier tests (2026-10-30 to 2026-11-12) said the 36 always freeze. They were wrong: the emulator's debugging hooks work by changing one byte of the game at each spot they watch, two of those spots sit inside the bytes this picture is read from, and the changed picture set the sound byte to a value that always froze.

Tool · Encounter explorer

Which MissingNo. does your name give?

Your name is 11 bytes in the game's memory: up to seven letters, an end mark, then blank 0 bytes. The old man's demo leaves those 11 bytes exactly where the game keeps its list of wild Pokemon, and the shore reads them in pairs, a level and then a species. The end mark is byte 80, a MissingNo. index number, and every blank 0 is 'M, MissingNo.'s twin. Type your name, or pick one of the names the game offers, to see the five Pokemon it summons and the game's own odds for each.

Or a name the game offers:

The naming screen's letters only, up to seven. RED, ASH and JACK are Pokemon Red's offers, BLUE, GARY and JOHN Pokemon Blue's.

Every typed name ends the same way: slots 4 and 5 always read blank bytes, so they are always 'M, at level 0 or 80. A name the game offers is different, because picking it copies the next names in the list as well, which is why RED meets no 'M at all. For every letter and the full table, use the Old Man Glitch Name Calculator, which runs this same engine.

Tool · Item duplication simulator

What MissingNo. does to your bag

The moment the battle starts, the game marks MissingNo. as seen in your Pokedex. It does that by setting a flag, numbered by Pokedex number minus 1, and 0 minus 1 is 255 again. Flag 255 sits 31 bytes past the start of the seen flags, which are only 19 bytes long. Byte 31 is the count of the sixth item in your bag, and the flag is its top bit, bit 7, worth 128. So the count does not go up by 128 every time: the bit is either off, and turns on, or already on.

The bag screen has room for two digits, so a count of 100 or more prints oddly: the game writes the tens as the tile that many places after the digit 0, and past 9 that is not a digit at all but a piece of whatever map or screen is behind the menu. The count itself is fine, and using the item takes one off as usual.

Gen 1 item bag after meeting MissingNo, the sixth item multiplied

The real bag screen after meeting MissingNo. with one Rare Candy sixth, captured in the game's own code in an emulator on Route 8. Here the sixth slot, a single Rare Candy, has become a stack of 129, and the tens place shows a tile of the map behind the menu.

The RAM proof: 0 minus 1 is 255

MissingNo.'s Pokedex number is 0. To mark a Pokemon as seen, the game takes its Pokedex number minus 1 as a flag number, and in one byte 0 minus 1 wraps to 255. Flag 255 is bit 7 of byte 31 of the seen flags, because 255 divided by 8 is 31 with 7 left over. The seen flags are only 19 bytes long. Right after them comes the number of items in your bag, then each item and its count, so byte 31 is the sixth item's count, and bit 7 is worth 128.

What the game holds as the battle startsValue read from RAM
MissingNo.'s Pokedex number (wPokedexNum)0
Flag number, 0 minus 1 in one byte (register C)255
Start of the seen flags (wPokedexSeen)$D30A
Byte written, $D30A + 255 / 8$D329, the sixth item's count
Bit set, 255 mod 8bit 7, worth 128
That byte before and after the battle5 then 133; 130 then 130; 200 then 200
; pret pokered, engine/battle/core.asm, as the wild Pokemon's data is loaded
    ld a, [wEnemyMonSpecies2]
    ld [wPokedexNum], a
    predef IndexToPokedex       ; MissingNo. gives 0
    ld a, [wPokedexNum]
    dec a                       ; 0 minus 1 = 255
    ld c, a
    ld b, FLAG_SET
    ld hl, wPokedexSeen
    predef FlagActionPredef     ; mark this mon as seen in the pokedex

Tested 2026-10-30 by playing it in the game's own code: normal saves on my own Red and Blue cartridge dumps, the old man, Route 20's shore column, all by button presses in an emulator (PyBoy), with the game's flag routine watched at the moment MissingNo.'s battle called it. The encounter itself is random, so this part rests on that one emulator; a second one (gambatte) agreed with it up to the old man, where the random rolls part the two. Yellow does the same thing one byte lower, at $D309 and $D328.

The item multiplication in one line: the game sets the top bit, bit 7, of the sixth item's count in your bag. A count under 128 goes up by exactly 128, so 5 becomes 133. A count of 128 or more stays the same, because that bit is already on. 'M does the same in Red and Blue, because its Pokedex number is 0 too.

The question every forum thread asks

Is MissingNo. safe? Does it delete your save?

Short answer: no, it does not delete your save. In Red and Blue, meeting MissingNo. changes one bit in your bag and overwrites part of the Hall of Fame record. Your saved game is not touched. In Yellow, 36 of the 39 MissingNo. can freeze the game, depending on your save memory.

  • Your bag. The battle sets one bit: bit 7 of the sixth item's count. No other item changes, a count of 128 or more is left alone, and meeting MissingNo. again changes nothing more. Save, and the new count is kept. Tested 2026-10-30 by playing it in the game's own code: the bit in Red, Blue and Yellow, the save in Red and Yellow.
  • Your Hall of Fame. MissingNo.'s compressed picture says it is 13 by 13 tiles, and the buffers it is unpacked into hold 7 by 7 tiles each. Unpacking it writes on past them, over the first 704 bytes of the Hall of Fame record that sits a little past the buffers in the cartridge's save memory: the first seven teams and part of the eighth. Those buffers are in the cartridge's own memory, so the damage is done the moment the battle starts, saved or not. If you have already entered the Hall of Fame, the PC can show those teams garbled. The fossil and ghost pictures fit, so those three never touch it. Your saved game sits in a different bank of that memory, which the picture code never selects. Tested 2026-11-11 in the game's own code in an emulator, in Red and in Blue: with the Hall of Fame area filled with a marker, the battle with index 31 changed bytes up to $A857 and no further, all 704 Hall of Fame bytes among them, and the three banks that hold the saved game came out byte for byte the same. A battle with a Rattata, the control, changed none of it.
  • Scrambled pictures. The garbled pictures people remember are MissingNo.'s own and the damaged Hall of Fame teams. Nothing else stays scrambled: after a MissingNo. battle, the next battle and a status screen drew exactly the same screen as after a battle with a Rattata. So the old advice to view a normal Pokemon's stats has nothing to fix, and nothing in the game puts the old Hall of Fame teams back. Tested 2026-11-11 in the game's own code in an emulator, Red and Blue: the second battle's screen, both picture areas of video memory and the status screen compared byte for byte.
  • Yellow. Yellow's shore never gives the old man's encounters, so the tests reached MissingNo. there by the trainer-fly trick with a Ditto. Of Yellow's 39 MissingNo. index numbers, 182, 183 and 184 (0xB6 to 0xB8, the slots that wear the fossils and the ghost) always give a battle you can run from. The other 36 set the bit and then battle or freeze depending on your cartridge's save memory: 31, 32, 50, 52, 56, 61, 62, 63, 67, 68, 69, 79, 80, 81, 86, 87, 94, 95, 115, 121, 122, 127, 134, 135, 137, 140, 146, 156, 159, 160, 161, 162, 172, 174, 175 and 181. When one freezes, nothing can be saved, and the save you had loads as before. Tested 2026-11-14 in the game's own code in an emulator with no debugging hooks: all 39 index numbers in four save memories (the blank one as a Game Boy and as a Game Boy Color), and every value of the sound byte for index 67 (the first 96 run one by one, the other 160 following the same cartridge rule, checked on 6 of them). Earlier tests (2026-10-30 to 2026-11-12) said the 36 always freeze. They were wrong: the emulator's debugging hooks work by changing one byte of the game at each spot they watch, two of those spots sit inside the bytes this picture is read from, and the changed picture set the sound byte to a value that always froze. One emulator (PyBoy).
  • Red and Blue battles. The same trainer-fly test, run through the game's own battle start for every number (31, 80, 135, 140 and 182 also played through by button presses), started a normal battle for each of the 39 MissingNo. index numbers in Red and Blue. None of them froze.
Specimen 0x1F · MissingNo. · Pokemon Red and Blue

MissingNo.'s type, stats, moves and cry

These are the values the game finds in those 28 bytes, row 255 of the base stats table, for every one of the 36 look-alike index numbers.

What the game readsWhereValue it gets
Its typestats byte 6BIRD a type cut from the finished game
Second typestats byte 7NORMAL
Attackstats byte 2136, higher than any of the 151 (Dragonite's 134 is the best)
Defensestats byte 30, none at all
Catch ratestats byte 829
Sprite sizestats byte 100x88, claims 8 by 8 tiles, but the buffer holds 7 by 7
Sprite locationstats bytes 11-12a pointer into data that is not a sprite
Starting movesstats bytes 15-18Water Gun, Water Gun, Sky Attack
HP
33
Attack
136
Defense
0
Speed
29
Special
6
Total
204

Moves it can learn. None by level: its level-up list is empty. By machine it takes 22 TMs (Mega Punch, Razor Wind, Swords Dance, Mega Kick, Toxic, Take Down, Double-Edge, BubbleBeam, Ice Beam, Blizzard, Submission, Seismic Toss, Rage, Thunder, Earthquake, Fissure, Psychic, Teleport, Sky Attack, Rest, Thunder Wave and Tri Attack) and two HMs, Cut and Fly. In Gen 1 a move's type decides the stat it hits with, so Sky Attack swings with that 136 Attack while Water Gun runs off a Special of 6.

The Bird type

Its first type reads as Bird, a category present in the code of Red and Blue but cut from every real Pokemon before release. Flying was kept, Bird was abandoned, and almost nothing of it survived: the type chart has no Bird rows at all, so the type does nothing in battle, but its name is still in the game's list of type names. MissingNo., reading raw bytes as a type, lands on it, making it one of the only creatures in the game to carry a type the designers deleted.

Why the picture looks like a backwards L

Every Pokemon sprite in Red and Blue is stored compressed, as two black-and-white layers stacked into one grayscale picture, and the Game Boy rebuilds it live with a little decompression engine. Scroll, and watch a real one come together.

sprite decode stage

Here is the whole secret of MissingNo.'s look: the machine you just watched does not check whether its input is a sprite. MissingNo.'s bytes point the decompression engine at data that was never a sprite, and it runs anyway. It unpacks, it delta-decodes, it stacks the layers, exactly as before, on bytes that mean nothing.

MissingNo sprite assembling column by column from garbage data
buffers A and B, delta decode, then combine into the finished sprite

What comes out is MissingNo.'s actual sprite, decoded honestly from the ROM: structured static with a strange, banded texture, because even garbage run through a real algorithm is not pure noise. The size byte then finishes the job. It claims the sprite is 8 tiles wide, but the display space the game copies it into is only 7 tiles across. When the copy reaches the edge it wraps to the next row one tile too soon, and the whole picture shears into the tall, hooked column players recognize. The shape is not a drawing. It is an off-by-one error, made visible.

That front picture comes from the same place in the cartridge, 0x1900, for all 36 look-alike slots, so it looks the same every time. Only its back picture, the one you see when you send it out, is read from video memory, so that is the view that changes with whatever the Game Boy drew before.

The three forms with a face

Three of the 39 slots hit a special case the developers wrote for other scenes, and wear a real, finished picture: the two dinosaur skeletons from the Pewter City museum and the ghost that haunts Lavender Tower before you have the Silph Scope. The special case writes only the picture and its size, so those three have no stats of their own: their numbers are whatever the last Pokemon the game loaded left behind. Each has its own page: the Kabutops fossil form, the Aerodactyl fossil form and the Ghost form.

Hear it, synthesized from the cartridge

A Pokemon's cry is three bytes: a base sound, a pitch and a length. Thirty of the 39 MissingNo. index numbers carry the same three, base 0x00, pitch 0x00 and length 0x00. Base 0x00 is the cry Nidoran♂, Nidorino, Sandshrew and Sandslash are built on, and length 0x00 is the shortest setting, which among the 151 only Magikarp also uses. The other nine MissingNo. carry cries of their own.

This is not a recording. I read MissingNo.'s three cry bytes from the ROM and rebuild the sound live in your browser from the Game Boy's own two pulse channels and its noise channel, the same way the hardware would. Press play.

base 0x00 pitch 0x00 length 0x00

Across five cartridges

People say MissingNo. like it is one thing. It is not. I decoded the same empty slot from five different versions, and they disagree. Red and Blue share identical data. Yellow moved things around. And the two original Japanese carts, Red and Green, are different machines underneath, so the accident lands somewhere else entirely.

MissingNo in Red and Blue, real Super Game Boy capture
Red / BlueMy own capture, Super Game Boy palette.
MissingNo in Pokemon Yellow, real capture
YellowMy own capture. Different data, a different shape, and the fiery palette Yellow gives it on a Game Boy Color.
VersionWhat changes
Red / Blue (US)The canonical MissingNo. Identical data between the two, same behavior. Shown above in the purple palette a Super Game Boy assigns it.
YellowDifferent data at the empty slot, so it comes out a different shape entirely (its stats read 178 HP, 19 Attack, 11 Defense, 0 Speed and 23 Special), and on a Game Boy Color it inherits that red and yellow fire palette. That is my real Yellow encounter above, next to my Red one, and you can see they are not the same creature.
Red / Green (JP)The originals. A smaller ROM with a differently shaped stats table, so the byte math lands on unrelated data. A different glitch entirely.

Why does MissingNo. have color?

The sprite itself has none. Like every picture in Red and Blue it is four shades, white, light gray, dark gray and black, and on an original Game Boy that is all you ever see. The color comes from the hardware around the game. On a Super Game Boy, Red and Blue pick a palette for each Pokemon by its Pokedex number, and MissingNo.'s Pokedex number is 0. Entry 0 in that palette table is the same one the game gives Mew, so the purple in my Red capture above is, quite literally, Mew's colors. Yellow runs the same lookup on a Game Boy Color, where that entry is white, yellow, red and black, which is why its MissingNo. burns red and yellow.

Does it still work in 2026?

Yes. Nintendo re-released Red and Blue on the Nintendo 3DS Virtual Console in 2016, and they shipped the glitch intact. The old man trick, the coastline encounter and the item duplication in the sixth bag slot all still run there. The 3DS eShop stopped selling games on March 27, 2023, so today only people who already bought it can download it again.

WhereStill works?
Original Game Boy cartridgeYes. The source of everything on this page.
Super Game BoyYes. Red and Blue show the colors of my Red capture above.
Game Boy ColorYes. Yellow gives it a red and yellow palette there, the one in my Yellow capture above. Red and Blue send their colors only to a Super Game Boy, so on a Game Boy Color they do not use the Mew palette of my Red capture.
3DS Virtual Console (2016 re-release)Yes. Nintendo’s re-release mainly changed its link features and toned down some flashing move animations, not the code this relies on, so it works there too.
Later remakes (FireRed, Let's Go, etc.)No. Rebuilt engines, the empty slot no longer overflows the same way.
After the encounter

What happens if you catch, level, evolve or trade it

Tool Throw a ball at MissingNo.
Is Cubone in your Pokedex?

Catching it. You can catch MissingNo. like any wild Pokemon, but what you get depends on Cubone. When a ball lands, the game checks whether you already owned the Pokemon, using the owned flag for Pokedex number minus 1, which is flag 255 again. The owned flags sit 19 bytes before the seen flags, so flag 255 of the owned list is the seen flag of Pokedex number 104, Cubone. If Cubone is not marked as seen, the game thinks this is a new Pokemon and opens a Pokedex page for it. That page cannot draw a Pokedex number of 0, so it falls back to Rhydon (index 1), and the Rhydon stays: the Pokemon added to your party is a Rhydon at MissingNo.'s level, with Rhydon's own moves. If you have seen Cubone, no page opens and you keep a MissingNo. Either way, Cubone is marked as seen afterwards.

Tested 2026-11-11 in the game's own code in an emulator, Red and Blue, with a Master Ball and MissingNo. index 31 at level 7, once with Cubone unseen and once seen. With a full party it goes to the PC box, which reads the same number (from the code, not played through).

Levelling it. It levels up, on an experience curve of its own: its growth byte, 26, points past the end of the game's six growth formulas. The game's own formula gives it 345,420 experience points at level 100, under half of what the fastest real Pokemon need (800,000). Its level-up move list is empty, so it learns nothing new, and its status screen draws no picture, because the game refuses to draw a Pokedex number of 0.

Evolving it. It never evolves. Its evolution list is empty. The one MissingNo. relative that does evolve is 'M.

Trading it. Between two Red or Blue games nothing checks it, so it arrives as the same MissingNo. Gold, Silver and Crystal refuse it: their Time Capsule turns index 31 into Scizor, compares the types it was sent, Bird and Normal, with Scizor's, finds they differ, says your friend's Pokemon appears to be abnormal and cancels the trade.

The experience curve: the game's own experience routine, run in an emulator for every level. Evolution and learnset: the game's own evolution and move routines, run in an emulator. Trading: from the code (pret's pokered, pokegold and pokecrystal), not played through.

The twin

'M (00) and how it differs from MissingNo.

'M is index number 0, the place before Rhydon. Its Pokedex number is 0 too, so it reads the very same stats, types, moves and picture as MissingNo.: 33/136/0/29/6, Bird and Normal, Water Gun, Water Gun and Sky Attack. In Red and Blue it sets the same item bit and does the same Hall of Fame damage. What it does not share is everything the game looks up by index number instead of Pokedex number.

MissingNo. (index 0x1F)'M (index 0x00)
Name on screenMISSINGNO.'M, read from past the end of the name list
Cry bytes0x00, 0x00, 0x000x18, 0xF7, 0x7E
Evolvesneverinto Kangaskhan at its first level up (Clefairy from level 128)
Learns by levelnothingPound at level 136
From the old man's coastfrom the letters G, H, J, M and S, some lower case letters and symbols, and the end markfrom every blank byte after a typed name, at level 0 or 80
From the Ditto glitchyes, all 39never: 0 means no opponent, so no battle starts
In Yellow182 to 184 safe; the other 36 battle or freeze, depending on the savea different glitch Pokemon with Pokedex number 176

Catching 'M has one more quirk, from the code: the battle decides you caught something by checking for a species number that is not 0, and 'M's is 0, so it is added to your team (as a Rhydon if Cubone is unseen, just like MissingNo.) and the battle carries on. The full story, with its Kangaskhan evolution played out, is on 'M's own page.

MissingNo. FAQ

What is MissingNo.?

MissingNo. is a glitch Pokemon in Pokemon Red and Blue. It is what the game shows when it reaches one of the 39 empty places in its list of 190 species numbers. The name is the developers' placeholder; its stats, types, moves and picture are read from data that was never meant to be a Pokemon.

How do you get MissingNo.?

Let the old man in Viridian City show you how to catch a Pokemon (answer NO when he asks if you are in a hurry), fly to Cinnabar Island without crossing grass or a cave, surf from the island's east edge and go up and down that column of shore squares. The Pokemon that appear come from the letters of your name. The Ditto glitch is the other way in.

Is MissingNo. safe? Will it delete my save?

It will not delete your save. In Red and Blue, meeting MissingNo. sets one bit of your sixth item's count and overwrites the first 704 bytes of the Hall of Fame record, so old Hall of Fame teams can look garbled. Your saved game sits in another part of the cartridge's memory and is never touched. In Yellow, 36 of the 39 MissingNo. can freeze the game, depending on your save memory.

Does MissingNo. duplicate items?

It adds 128 to the count of the sixth item in your bag when that count is under 128. The game marks MissingNo. as seen with flag number 255, and that flag is the top bit of the sixth item's count. One Rare Candy becomes 129; a stack of 128 or more stays the same.

Can you catch MissingNo.?

Yes. If Cubone is already marked as seen in your Pokedex, you keep a MissingNo. If it is not, the game opens a Pokedex page that cannot show Pokedex number 0, falls back to Rhydon, and you get a Rhydon instead.

Is MissingNo. in Pokemon Yellow?

Its data is, but the old man's coast does not work in Yellow. The Ditto glitch reaches all 39 MissingNo. index numbers. 182, 183 and 184 (the fossil and ghost forms) always battle normally. The other 36 battle or freeze, mostly depending on bytes of your cartridge's save memory rather than on the number you pick.

Why does MissingNo. sometimes freeze Pokemon Yellow?

Only sometimes, and the reason is traced in the game's code. 36 of Yellow's 39 MissingNo. read the picture of Pokedex number 0, whose address is $0006, the very start of the cartridge, where there is no picture. Unpacking those bytes takes about 630 frames of black screen (about 10.5 seconds) and writes through the Hall of Fame record and into the game's working memory, including the byte at $C0EF that tells the sound code where its music is. That byte's new value comes from save memory bytes the game never clears. Then MissingNo.'s cry jumps to address $6BD4 in whatever part of the cartridge the byte names: a real sound routine or harmless code and the battle goes on, other code and the game freezes. 182, 183 and 184 get the fossil and ghost pictures directly, so they always battle.

Why does the game pause before MissingNo. appears?

The pause is the picture being unpacked. MissingNo.'s compressed picture says it is 13 by 13 tiles, and unpacking it took 108 frames, about 1.8 seconds, in Red, against 16 to 41 frames for each of the 151 real Pokemon. 'M reads the same picture and pauses the same way. The game is not saving: no save routine runs, and your saved game sits in a different bank of the cartridge's memory from the picture buffers.

What type is MissingNo.?

Bird and Normal. Bird is a type left in the code of Red and Blue but given to no real Pokemon, and the type chart has no entries for it, so it does nothing in battle.

What is MissingNo.'s Pokedex number?

000. Every MissingNo. has Pokedex number 0, and the game's sums with that 0 are behind nearly everything it does.

Fight it yourself

This is my from-scratch recreation of the Red battle engine, not an emulator, running natively right here on the page. The enemy is preset to MissingNo., with its real Bird typing, its 136 attack and its zero defense. Pick your own fighter and see how a battle against the empty slot actually plays out.

Want this fight on your own site? The battler embed is free to use as long as its credit line stays, and MissingNo. is one of the opponents it can start with.

YOUR TEAM · tap a slot to edit
ENEMY TEAM

Arrow keys move, Enter or Z is A, Escape or X is B. Or just tap the screen.

Related pages

A personal note

My history with this thing

I have been GardenFlouer online since I was a kid, and glitch Pokemon are a big part of why. Here is MissingNo.'s cry, and, if the tape still exists, the video of a much younger me finding it for the first time.

The cry

The day I found it

Every number and every sprite on this page was decoded from a Pokemon Red ROM by reproducing the game's own reads, and the behavior was tested in the game's own code in an emulator. Thanks to pret's disassemblies and the Glitch City community, whose years of notes pointed at what to test. Part of The Glitchhouse, a field guide to the broken Pokemon of Red and Blue.