Template:Looking for

Operator:Joe Mach
Compatible human:{{{human}}}
Compatible AM/FM-ian:{{{FM}}}
Compatible UMA:{{{UMA}}}
Compatible Wizard:{{{Wizard}}}
EM-Wave Change:Template:Emwavechange
Attacks:Blast Explosion, Fire Tornado, Blast Rain
Battle Chips:{{{chip}}}
Main site:
in games:
MegaMan Battle Network 6
Other appearances: MegaMan NT Warrior
Voice actor:{{{voiceactor}}}

BlastMan.EXE is Joe Mach's fire NetNavi, and is the first boss in MegaMan Battle Network 6. He is first encountered near the beginning of Megaman Battle Network 6. He tricks Mick into operating him, allowing him to hack the Robot Control Computer, causing the security robots to go out of control and attack everyone in the school. To get to him, one must go through a maze, which involves putting out flaming Mr. Progs while standing behind blocks to avoid getting hit by the fireballs he throws at you. When BlastMan is defeated by Lan he swore he would get revenge.

He is later encountered with DiveMan.EXE when they both attempt to kidnap Roll.EXE, GutsMan.EXE, and Glyde.EXE. Though they are defeated, they buy enough time for CircusMan.EXE to do the dirty work.

He can be found in Central Area 2, in his EX form. After defeating the EX form he will appear randomly in Central Area 2 in his SP form. His RV form in the Graveyard possesses 2000 HP. He has the following attacks:

  • Blast Explosion: Shoots an explosion down the row.
  • Fire Tornado: Blastman will shoot instead a fire-attributed tornado down your row. He will try to stand at the front of his area for this attack.
  • Blast Rain: First, tiny harmless enbers will travel in one direction across the screen. These indicate which way the large fireballs which follow will fly. The only way to dodge these fireballs is to place one of the large metal blocks between you and them.



From MMKB, a Wikia wiki.

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.