Season
Power ratings
| Event | CCWM | OPR | DPR | Alliances | Fit |
|---|---|---|---|---|---|
| Saratoga VEX V5 Robotics Competition™ #1: Override H | -20.4 | 25.1 | 45.5 | 7 | R² 0.451 · ±28.25 pts |
| Tri-Valley VEX V5 Robotics Competition #1: HS&MS onl | 29.2 | 37.7 | 8.4 | 8 | R² 0.457 · ±28.46 pts |
| DRC VEX V5 Robotics Competition #1: HS & MS, Remote | -4.6 | 33.8 | 38.4 | 7 | R² 0.48 · ±26.39 pts |
OPR is what this team contributed to its own alliance's score, DPR what it allowed the opposing alliance, and CCWM the difference. All three are solved across every alliance at that event at once, so they do not depend on who the team was paired with — which win rate and average score both do.
Read them as rankings, not quantities. The fit column is honest about the precision: these explain roughly a third of score variance, and each team's figure rests on about five alliances. DPR can even come out slightly negative, which is the least-squares fit overshooting rather than a team causing negative points.
A team playing pure defense suppresses opponents instead of scoring, so it shows as low OPR and low DPR. That is why CCWM is the column to lead with — at the Mall of America event the undefeated winner ranked 6th on OPR and 1st on CCWM.
Allies
| Team | Name | Together | Eliminations | Record | Win rate |
|---|---|---|---|---|---|
| 2715N | Night Fury | 4 | 2 | 1–2–1 | 25% |
| 12790X | Alpaca | 2 | 1 | 1–1–0 | 50% |
| 82777C | Coin Toss | 1 | 1 | 0–1–0 | 0% |
| 1468A | _Underscore | 2 | — | 1–1–0 | 50% |
| 1000A | Foothill Robotics | 1 | — | 0–1–0 | 0% |
| 11551A | Super Dragon Slayer | 1 | — | 1–0–0 | 100% |
| 3134G | Dublin Robotics GearShift | 1 | — | 1–0–0 | 100% |
| 3303W | Dublin Robotics Wyvern | 1 | — | 1–0–0 | 100% |
| 3332A | Astrabot | 1 | — | 0–1–0 | 0% |
| 3376A | Robolabs Artemis | 1 | — | 1–0–0 | 100% |
| 3457V | Robolabs Veritas | 1 | — | 0–1–0 | 0% |
| 3457Z | Robolabs ZBOT | 1 | — | 0–1–0 | 0% |
Top 12 of 17 distinct allies.
Sorted by elimination partnerships first, then by how often they played together. That order is the point: a qualification partner is a random draw, so playing with someone repeatedly says nothing about either team. An elimination partner was chosen in alliance selection — so even one says something, because it is either who picked them or who they picked.
The record is the pair's record in the matches they played together, which is the only record that describes the pairing rather than either team on its own.
Events
Matches
Robot analysis
Nothing here yet, and the reason is worth stating plainly rather than filling the space with numbers that do not mean what they appear to.
Tracking produces four anonymous tracks per match — robot 0 through robot 3 — and nothing in the video says which one is 5776T. Team plates measure about 17 pixels tall in this footage, so reading them is out of reach. Attribution has to come from the match schedule plus each robot's starting tile, which is not built.
Until it is, per-robot measurements — distance travelled, time in each zone, contact events, build-style clustering — live on the match pages, unattributed. They are deliberately not rolled up here, because a season average over tracks that may belong to the opposing alliance would be worse than no average at all.
Robot videos
Not searched yet. The daily search reaches every team in turn, or run python -m integrations.youtube --team 5776T now.
Match footage
No footage linked to this team's matches yet. A match page takes a stream link and the time the match starts in it.