Season
Power ratings
| Event | CCWM | OPR | DPR | Alliances | Fit |
|---|---|---|---|---|---|
| WestMech V5 Override Early Season First Qualifier: M | -19.6 | 11.2 | 30.8 | 6 | R² 0.599 · ±19.33 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 |
|---|---|---|---|---|---|
| 14353S | Zebra Robotics- Dragon Volts | 1 | 1 | 0–1–0 | 0% |
| 2088V | To be confirmed | 1 | — | 0–1–0 | 0% |
| 2551A | Bee | 1 | — | 1–0–0 | 100% |
| 3300Z | Solar | 1 | — | 0–1–0 | 0% |
| 45519S | Synthesis | 1 | — | 0–1–0 | 0% |
| 45519Z | Zenith | 1 | — | 0–1–0 | 0% |
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.
Matches
| Date | Event | Match | Side | Partners | Opponents | Score | Result | Analysis |
|---|---|---|---|---|---|---|---|---|
| 2026-10-24 15:28 | WestMech V5 Override Early Season Firs | Qualifier #5 | red | 45519S | 3388G 2088Y | 27–30 | loss | no footage |
| 2026-10-24 15:49 | WestMech V5 Override Early Season Firs | Qualifier #8 | blue | 3300Z | 210K 2088X | 0–57 | loss | no footage |
| 2026-10-24 16:24 | WestMech V5 Override Early Season Firs | Qualifier #13 | blue | 45519Z | 3300Z 3388H | 60–82 | loss | no footage |
| 2026-10-24 16:59 | WestMech V5 Override Early Season Firs | Qualifier #18 | red | 2551A | 3388Z 210E | 64–39 | win | no footage |
| 2026-10-24 17:48 | WestMech V5 Override Early Season Firs | Qualifier #25 | blue | 2088V | 210T 2088M | 20–48 | loss | no footage |
| 2026-10-24 | WestMech V5 Override Early Season Firs | QF #3-1 | red | 14353S | 2551A 2088M | 8–45 | loss | no footage |
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 45519B. 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 45519B 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.