Race for Eggs WIKI
Play on Roblox

Who writes this, and how it is sourced

About the Race for Eggs Wiki

An independent, unofficial fan project for Race for Eggs, built on four evidence labels and a short list of things it will never invent.

Who runs this site

An independent fan project, written by players of the game.

Race for Eggs Wiki is an unofficial fan resource for the Roblox game Race for Eggs. It is written and maintained by players of the game who wanted one place where the numbers were labelled and the gaps were admitted, rather than filled in with guesses.

This is not a company and there is no staff list to publish. The site has no advertising contract with the developer, receives no data feed from them, and does not take payment for coverage. Everything published here comes from the public sources listed on the sources page.

The one claim the maintainers make is consistency: the same four evidence labels are applied to every row of data, and a value that cannot carry a label is not published as a number.

Unofficial and unaffiliated

Who this site is, and who it is not.

Publisher
Race for Eggs Wiki (unofficial fan site)
Affiliated with Roblox
No
Affiliated with developer
No
Data feed from developer
None

!Not an official source

This site is not affiliated with Roblox Corporation or with xFrozen x Dudes. For anything binding — codes, purchases, moderation or account questions — use the game's own page on Roblox.

Which Race for Eggs this covers

Several Roblox games share similar names, and search engines mix them up.

This wiki covers one game: Race for Eggs, the race-and-hatch game by xFrozen x Dudes. It does not cover Race Clicker, Race Simulator, or any other Roblox game whose name overlaps with this one.

If a code you found somewhere else does not work here, the likely explanation is that it belongs to a different game with a similar name. We list only codes reported for this game, and the one unconfirmed outlier is marked so that it can be recognised rather than trusted.

The reliable check is the developer: everything on this site is about the game by xFrozen x Dudes, and the community group linked in the footer is that developer's group.

How we label evidence

Four labels, applied to every data row on this site.

1OfficialRead from a Roblox endpoint, or stated by the developer in the game's own description. Anyone can re-check it against the same public address.
2ReportedOne credible outlet carries it and we could not corroborate it. Useful and dated, but clearly marked as a single source.
3CommunitySeveral independent players or outlets agree on the same value. Consensus rather than official confirmation, and still labelled.
4UnknownThe developer has not published it and no reliable source covers it. The row stays visible and says Unknown instead of guessing.

A row with a label is a claim with a source. Official, Reported, Community and Unknown are the only labels used, and a row that cannot carry one is not published as a number. When a value changes, the label is re-checked and the snapshot date on the page moves with it.

What this site does not publish

Four categories we deliberately leave out.

  1. 1

    Invented codes

    A code appears here only if a source we can name reports it for this game. A long list of dead codes looks thorough and wastes your time.

  2. 2

    Drop rates and hatch odds

    The developer has never published hatch percentages. A wrong drop rate sends players to the wrong egg, so those rows say Unknown.

  3. 3

    Patch notes

    We do not paraphrase an update we have not read. An update entry links to the developer's own post, or states that no public notes exist.

  4. 4

    Pet income values

    Income is not published in-game or by the developer. We show the pet's evidence label and leave the income row Unknown rather than estimating it.

The pattern is the same in each case: if the value cannot be traced to a public source, the page says so. An honest Unknown is more useful than a confident number that is wrong.

Corrections and removals

If something here is wrong, we want to fix it.

  1. 1

    Send the correction

    Say which page and which row is wrong. A link to the developer's post or to a Roblox endpoint is enough to start.

  2. 2

    We re-check it

    The value is measured against a listed source. If it cannot be confirmed, the row is relabelled rather than left as fact.

  3. 3

    The dates move

    An accepted change updates the snapshot date and the affected source notes together, so the freshness signal stays honest.

Removal requests follow the same route: name the page and what should come out. The contact channel is described in the privacy policy, and requests about a person's own work or details are handled first.