FANDOM


Triterobot

Triterobot was Team Mousetrap's entry into Series 3 of Robot Wars. Like Steg-O-Saw-Us, Triterobot was a reserve (although it is not clear who it replaced) and did not receive a televised introduction. It lost its only battle against Evil Weevil. It's name is believed to be a pun on Triceratops, a type of herbivorous dinosaur.

Robot History Edit

In Round 1 of the Third Wars, Triterobot went up against future Semi-Finalists Evil Weevil. As soon as Activate was called, Triterobot moved quickly towards Evil Weevil and collided with it. After driving into Sergeant Bash's CPZ, Evil Weevil drove onto the Arena Wall and was spiked by Triterabot. Evil Weevil then pushed Triterobot towards Sergeant Bash, who became impaled onto the House Robot by one of its spikes. Then Evil Weevil pushed Triterobot around the Arena floor until reaching Sir Killalot's CPZ. There, Evil Weevil released Triterobot who promptly impaled one of its spikes into Evil Weevil's fibreglass armour and began to smoke copiously. The battle was briefly paused due to the perceived fire hazard, but allowed to continue as the house robots separated the two machines, but Triterobot had lost a lot of its power during the "smokescreen". Evil Weevil then attacked Triterobot and turned it on its side, where neither sets of Triterobot's castors touched the ground. Thus, it was stuck on its side and Evil Weevil pushed the immobile robot towards the pit. Missing the final push by instead driving in a curving arc, the House Robots closed in on Triterobot, however Evil Weevil attacked Shunt to help Triterobot, who were enjoying the punishment being inflicted upon their robot.

Results Edit

Series Event Round Opponent(s) Results
UK Robot Wars Series 3 Heat L Eliminator Evil Weevil Lost

Wins/Losses Edit

  • Wins: 0
  • Losses: 1

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.