The evidence ledger
Data Sources & Verification
A clear line between what the game says, what players report, and what is still unknown.
“Official” means a Roblox or developer record supports the stated claim. “Community reported” means a player capture or outside guide supplies a lead that this wiki has not repeated in-game. Unknown numbers stay blank. Each date describes a specific check and should not be read as proof that every value was retested.
Directly checked in the live game, or stated by an official Roblox game record. Each claim says which one.
Published by a game guide or player but not independently tested by this wiki. Codes currently sit here.
No suitable evidence yet, or reports conflict. We leave specific values blank.
Source order
- Direct in-game verification with a dated result.
- The official Roblox experience and badge records.
- Developer announcements and official community channels.
- Reliable gameplay captures where the value is visible.
- Community reports and independent guides, used as leads with a report label.
Multiple third-party lists repeating a code do not become an in-game test. A Roblox badge award rate does not become an egg or trait drop rate. An event listing does not prove its announced contents are already live.
Primary records checked for this edition
- Official Race Horses experience page — developer description and event listing.
- Roblox game API — game identity and stored build update timestamp.
- Roblox badge API — hatch rarity and progression badge descriptions.
- Gorilla Grafters community announcement — owner announcement dated Sep 17, 2026, confirming the HORSES code reward, care events and bigger stables.
Code report sources
The developer announced the HORSES code and its reward, but its current redemption status has not been tested by this wiki. Current reported active statuses are attributed on the codes page to Pro Game Guides. Destructoid supplies one expired-code report. These are third-party status reports, so the site does not claim to have redeemed the codes.
Egg and horse gameplay capture
A Race Horses gameplay video published Sep 25, 2026 shows six shop egg names and dollar prices, plus an individual horse card. Each egg record links to the relevant point in the video and shows the date we checked the source. We label these observations Community reported because we have not repeated them in our own game session. The recording does not establish current stock, a complete egg list, horse pools, hatch odds or a fixed horse roster.
What each date means
Last game update comes from the official game API. Database updated means our saved source-backed data changed. Codes source checked means published reports were reviewed. Last tested is reserved for an actual in-game redemption check, and stays empty until then.
Current record: game update Sep 24, 2026 UTC; database update Sep 25, 2026; code sources checked Sep 25, 2026; in-game code test Not verified yet.
Found a conflict or a newer game card? Prepare a correction report with the exact value, source and capture date.
Claim by claim
Examples of what evidence supports
| Evidence | Supported claim | Claim it does not support |
|---|---|---|
| Official hatch badge | A named hatch milestone or label exists. | The chance to hatch it from a specific egg. |
| Visible shop frame | The egg name and price shown in that dated recording. | Today’s price, a complete shop list or the egg’s pool. |
| Developer code announcement | The announced code and reward. | Current redeemability on your account. |
| One horse card | The values shown for that horse in that capture. | A fixed stat for every horse with a similar appearance. |
When sources disagree
We compare the exact claim, its date and the screen or record that produced it. A newer live shop price can supersede an older capture for that egg, while unrelated prices stay as they were. An official event listing can confirm that a feature was announced without proving it appeared in a particular server. An in-game code result may change a reported status, but the result must include the date and code text.
Dates are attached to the action they describe. A source-check date is when we reviewed a page or capture. A game update timestamp is metadata about the Roblox experience. A last-tested date requires an actual game action and result. We do not refresh those dates merely because a site page was rebuilt.
Why some ledgers have no rows
The horse, trait and stable pages have useful official context but no dependable level-by-level or name-and-effect data in the current saved sources. They remain indexable guides because they answer what can be established and how to check a current value. A row is added when the specific name or number has its own dated support; unknowns are not turned into zeroes or estimated rates.
Quick reference
Common questions
Does an official badge prove a drop rate?
No. Badge descriptions can establish a milestone or label. Award rates count badge ownership among players and do not describe an egg's roll probability.
What does a source-check date mean?
It means the cited source was reviewed on that date. It is separate from the date a code was redeemed or a value was observed in a live server.
Can one video establish every egg or horse?
No. A frame can support the visible name and number at that time. It cannot establish a complete roster, hidden odds or current prices after later changes.
Keep exploring