Vermicious kenid

Vermicious Kenid was a lightweight robot which competed in Seasons 3.0 and 4.0 of BattleBots. It was a two wheeled wedge-shaped robot armed with a rear horizontal spinning disc (later a bar). It performed decently in competition, reaching the round of 64 in its debut season but losing its first match in Season 4.0.

It was named after the "Vermicious Knids" - a natural predator of Oompa Loompas according to Charlie and the Chocolate Factory.

Robot History Edit

Season 3.0Edit

Vermiciouskenid sf01

Vermicious Kenid's first ever match in BattleBots was against Land Mine. Vermicious Kenid won on a 26-19 judge's decision and advanced to the final preliminary round, where it faced Mad Cow. Vermicious Kenid won the match by KO at 1:44 and advanced to the TV rounds, where it faced Crashius Clay. Crashius Clay won on a 30-15 judge's decision and Vermicious Kenid was eliminated from the tournament.

Because it lost in the round of 64, Vermicious Kenid couldn't participate the lightweight consolation rumble at the end of the tournament.

Season 4.0Edit

Vermicious Kenid only fight in Season 4.0 was against UGV Scorpion in the second preliminary round. UGV Scorpion went underneath Vermicous Kenid's spinning bar, which was too high to hit. UGV Scorpion rammed Vermicous Kenid once and then slammed it against the spikestrip twice, immobilizing the spinning bar entirely. Neither bot was under terribly good control, but UGV Scorpion was strong and fast and Vermicous Kenid was slow and weak. Vermicous Kenid had an opportunity late in the match, when UGV Scorpion lost one side of its drive, but didn't take advantage of it. In the end, UGV Scorpion won on a 36-9 judge's decision and Vermicious Kenid was eliminated from the tournament again.

Results Edit

Wins/Losses Edit

  • Wins: 2
  • Losses: 2

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.