Season
A Teamwork match is played with another team for a single shared score, so these are scoring figures, not a record — there is nobody to beat.
Scoring
OPR, DPR, CCWM and Elo all measure a team against an opponent: OPR separates a team from its partners by what the two alliances scored, and Elo moves on a win or a loss. A Teamwork match has neither, so none of them are computed for VEX IQ — the scoring figures above are the season view, and each event's own ranking is on the event page.
Allies
| Team | Name | Together | Eliminations |
|---|---|---|---|
| 295C | PART C | 1 | — |
| 295D | Robo Reapers | 1 | — |
| 295E | T0tB0t5 | 1 | — |
| 295H | Jazzy Jays | 1 | — |
| 295P | PART P | 1 | — |
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 | Played with | Score | Analysis |
|---|---|---|---|---|---|
| 2026-10-23 21:32 | Placer Robotics League: VIQRC ES Level | Practice #12 | 295H | 60 | no footage |
| 2026-10-23 21:57 | Placer Robotics League: VIQRC ES Level | TeamWork #12 | 295P | 80 | no footage |
| 2026-10-23 22:19 | Placer Robotics League: VIQRC ES Level | TeamWork #23 | 295C | 48 | no footage |
| 2026-10-23 22:33 | Placer Robotics League: VIQRC ES Level | TeamWork #30 | 295E | 63 | no footage |
| 2026-10-23 22:51 | Placer Robotics League: VIQRC ES Level | TeamWork #39 | 295D | 48 | 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 295M. 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 295M 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.