DT · GB · week 3
Anthony Campbell
66.0%
P(plays)
PLAY
our call
6 h
hours before kickoff
Baseline for his position and injury: 67.5% — the share of comparable cases that play. The model learns the departure from that, not the rate itself. Model: earliness/offset v1 (trained on 4497 cases, 2023-2025)
Every call we made on him
Appended, never overwritten. If we changed our mind, the change is here.
| Made at (UTC) | Call | P(plays) | Lead |
|---|---|---|---|
| 2026-09-24 01:47 | SIT | 45.4% | 22 h |
| 2026-09-24 03:05 | PLAY | 66.0% | 21 h |
| 2026-09-24 12:58 | PLAY | 66.0% | 11 h |
| 2026-09-24 13:00 | PLAY | 66.0% | 11 h |
| 2026-09-24 13:00 | PLAY | 66.0% | 11 h |
| 2026-09-24 13:01 | PLAY | 66.0% | 11 h |
| 2026-09-24 13:01 | PLAY | 66.0% | 11 h |
| 2026-09-24 13:02 | PLAY | 66.0% | 11 h |
| 2026-09-24 13:10 | PLAY | 66.0% | 11 h |
| 2026-09-24 14:04 | PLAY | 66.0% | 10 h |
| 2026-09-24 14:05 | PLAY | 66.0% | 10 h |
| 2026-09-24 14:33 | PLAY | 66.0% | 10 h |
| 2026-09-24 14:34 | PLAY | 66.0% | 10 h |
| 2026-09-24 14:35 | PLAY | 66.0% | 10 h |
| 2026-09-24 14:36 | PLAY | 66.0% | 10 h |
| 2026-09-24 15:16 | PLAY | 66.0% | 9 h |
| 2026-09-24 15:18 | PLAY | 66.0% | 9 h |
| 2026-09-24 15:52 | PLAY | 66.0% | 8 h |
| 2026-09-24 15:53 | PLAY | 66.0% | 8 h |
| 2026-09-24 15:54 | PLAY | 66.0% | 8 h |
| 2026-09-24 15:58 | PLAY | 66.0% | 8 h |
| 2026-09-24 17:13 | PLAY | 66.0% | 7 h |
| 2026-09-24 17:15 | PLAY | 66.0% | 7 h |
| 2026-09-24 17:17 | PLAY | 66.0% | 7 h |
| 2026-09-24 17:20 | PLAY | 66.0% | 7 h |
| 2026-09-24 17:35 | PLAY | 66.0% | 7 h |
| 2026-09-24 17:35 | PLAY | 66.0% | 7 h |
| 2026-09-24 17:42 | PLAY | 66.0% | 6 h |
| 2026-09-24 18:04 | PLAY | 66.0% | 6 h |
What the club reported
| First seen (UTC) | Practice | Game status | Team |
|---|---|---|---|
| 2026-09-24 02:55 | Limited Participation in Practice | — | GB |
| 2026-09-24 06:15 | Limited Participation in Practice | Questionable | GB |
What this page cannot show
His depth-chart position, snap history and previous injuries inform the model but are not published here — they live in the research corpus, not in the product database, and this site reads only the product API. The absence is a boundary, not a gap in his record.