What the official description establishes
Players pull eggs back to their farms, hatch those eggs, and earn money from the resulting Brainrots, including offline cash. Strength upgrades are advertised as the way to pull bigger and heavier eggs.
The official listing does not name every egg or animal, publish hatch odds, define a rarity order, or list base income. This page therefore focuses on decisions you can verify in your current game instead of presenting a guessed database.
Choose an egg by full-run value
| Question | Read or measure | Decision |
|---|---|---|
| Can it move? | Visible requirement or a direct test | Train first if it does not move. |
| Can it get home? | Successful deliveries ÷ attempts | Prefer the route you can repeat. |
| How long does one cycle take? | Pull, recovery, placement, and hatch time | Include every stage, not just travel. |
| What can it produce? | Official pool UI or your dated hatch records | Do not infer a pool from one result. |
| Does it improve the farm? | Income before and after under the same modifiers | Keep collection and income goals separate. |
Audit one hatch from egg to income
A field screenshot proves only that an egg appeared there. A hatch-result screenshot does not establish its probability. Keep each claim tied to the frame that actually supports it.
| Field | What to record |
|---|---|
| Egg identity | Exact displayed name; do not infer it from color alone. |
| Pull context | Current strength, route, attempts, and server date. |
| Timer | The value shown on this exact egg. |
| Result | Exact animal or Brainrot name and any visible variant. |
| Income | Displayed rate plus every active modifier or boost. |
| Evidence | Readable frames for the egg, result, and income display. |
Decide which hatch belongs on the farm
For an income goal, compare the farm’s measured rate with each candidate under the same boosts. If the game shows individual rates, record them; if it only shows the total, swap one item at a time and run equal-duration samples.
Keep a lower-income result when it serves a stated collection or testing goal. Otherwise, replace the weakest verified producer first after recording its exact name and rate.
| Farm decision | Minimum evidence |
|---|---|
| Keep for income | Repeatable positive income contribution under known modifiers. |
| Keep for collection | Exact identity or variant that fills your collection goal. |
| Replace | A controlled comparison showing another hatch performs better. |
| Unknown | Conflicting displays, active boosts, or no clean before/after sample. |
Compare eggs with value per minute
A useful session metric is farm-income increase per minute spent obtaining the hatch. Divide the measured permanent cash-per-second increase by the total minutes spent pulling, recovering, placing, and hatching. Use it only when the before-and-after farm samples are comparable.
A harder egg can still be a worse farming choice if failed pulls consume most of the session. A common egg can be useful when its route is fast and the current farm has weak slots. These are decision principles, not claims about a specific egg.
Record hatch odds without overstating them
Use an official probability display when the game provides one. Without that, report the sample as counts: for example, “3 of 10 observed hatches under these conditions,” rather than declaring a permanent 30% drop rate.
Keep the egg name, sample size, date, server version, luck boosts, and event state with every observation. Small samples are volatile and cannot establish a complete pool.
Current database coverage
Verified named egg records: none published yet. Verified named pet records: none published yet. Verified official odds: none published yet. This explicit gap prevents community names and numbers from silently becoming official through repetition.
The page is complete as a hatching and farm-management guide. Named database rows will be added only when readable in-game evidence or a first-party source supports them.