25,000
Five batches of 5,000; the last finished 9:12 AM ET.
DraftKings Classic daily fantasy
Build NFL lineups against the field, not against a projection.
The field is everyone else in the contest. We model it. Every projection comes as a range, worst case to best case.
- Simulations per slate
- 25,000 Derived: Arithmetic on the run log: 5,000 per batch, 25,000 in total.
- Games simulated together
- 12 Fixture: The Week 3 main slate in the fixture week.
- Priced players
- 300 Fixture: The Week 3 price file: 297 matched to names, 3 waiting on a decision.
The work behind it
The claim is above. Here is the work.
This is the real screen, in the fixture week (Week 3). Twelve games run together. Three hundred priced players. One figure withheld, because the prize structure is an assumption. Every number on it is labeled Fixture.
3 Fixture: Week 1, Week 2 and this week's slate, each with a saved price file.
Slates captured since Week 1
150 Fixture: Twenty cash games and a hundred and thirty tournaments in one build.
Lineups in one build
2 Measured: Week 1 and Week 2 were settled and scored against their payout lines.
Weeks settled and scored
1,792nd of 32,679 Measured: Week 1, the Classic main slate: our best lineup's finishing position.
Best big-field finish so far
What you get
Four things a spreadsheet cannot do for you.
Every number on the screen tells you where it came from. Prices come from the file you imported. Points come from a run you can open. Results come from the contest's own export. When we cannot source a number, we say so instead of guessing.
We play the whole slate out, all twelve games at once, 25,000 times. It is one correlated simulation, so players who score together move together, the way they do on Sunday. We model the field too. For every player we project his ownership (the share of entries that will pick him). That shows you the chalk (where the field piles up) and your leverage (where our numbers disagree with the field).
The whole slate, played out together
A stack (players from one team) rises and falls as one, the way it does on the field. Twelve games, one simulation, no unrelated guesses.
Fresh data, with the minute it was read
Prices and injury news carry a timestamp. If an update failed, we say so. Stale data is labeled where you see it, never quietly kept.
An assistant that cites its numbers
Ask why a player is in the lineup. You get the run it came from. If we do not know, we say so instead of guessing.
Nine players, chosen before the first kickoff
Everything on the screen is there to make that one choice easier. The evidence sits beside each name, ready before entries close.
Show your work
Four numbers, and where each one came from.
A landing page can print any figure it likes. These are the numbers the fixture week actually holds, including the one we are behind on. Each one tells you where it came from.
- Simulations per slate
- 25,000
- Every stat a fantasy point is built from, simulated together in one run.
- Entries in the contest we scored
- 32,679
- The Week 1 field our best lineup finished 1,792nd in.
- Lineups in one build
- 150
- Twenty cash games and a hundred and thirty tournaments (GPP).
- Points behind the sportsbooks, quarterbacks
- 0.2
- Three weeks in, across 45 quarterbacks with a price. Behind, not ahead.
Fixture Measured All four come from the one fixture week this page uses. Each is labeled where you see it.
“Show the number. Show where it came from. When we cannot source it, say so. Where the prize structure is an assumption, the return is withheld and the reason is printed in its place.”
Early access
Join the waitlist.
Access opens by invitation. Leave your email and we will send one confirmation now, then an invitation when your turn comes. It commits you to nothing and costs nothing.