FIRST Robotics Competition Blog

2018 Season by the Numbers

Some awe-inspiring numbers from the 2018 FIRST Robotics Competition POWER UP season, and 2018  ‘usage reporting’ data! 

Jun 14, 2018 Written by Frank Merrick.




Here are some numbers from the FIRST POWER UP season we wrapped up in April.

Minutes Twitch viewers spent watching official FIRST Robotics Competition events on FIRST Twitch channels

Total points scored in non-practice matches

Views during events on FIRST Robotics Competition Twitch channels

Attendees at FIRST Championship

Power ups played

Motor controllers used*

Non-practice matches played

Encoders used*

Teams not coding in C++, Java, or LabVIEW*

FIRST Robotics Competition field sets in use worldwide

8 minutes 4 seconds
Average match cycle time

4 minutes 58.027 seconds

Cheetah running fast

Fastest recorded match cycle time, Wisconsin Regional Match Q50

And Finally, 205

Days until Kickoff for the 2019 game DESTINATION: DEEP SPACE!



* The FIRST Robotics Competition software has a feature called ‘usage reporting’ that tracks what WPILib objects are created in each team's code and reports that data back to the field when the robot is connected. Here’s the full set of usage data from the 2018 season, and some notes from Kevin O’Connor, FIRST Robotics Competition Robotics Engineer:

  • The data has been semi-anonymized. Team numbers have been replaced with rookie years and the data has been resorted so teams are not in order by team number.
  • We can only track the objects teams create in code. If a team creates extra motor controllers that aren't on the robot, they will still be captured by this system. If a team creates motor controller objects of the wrong type, that wrong type will be captured by this system.
  • Counted objects and TRUE/FALSE show the largest number of any given object used in any one match (i.e. if a Robot had 2 Encoders in match 1 and 3 Encoders in match 7, 3 will be reported). Language and Framework report what was used in the last recorded match.
  • Some objects naturally result in double counting (Encoders use Digital Inputs).
Back to Blog

Add new comment