Raise an Anomaly Egg Stealing: How to Steal an Egg and Escape

Quick answer

An egg run is a four-part loop — scan the target, grab, escape, deposit. Compare the guard's live recommended-speed label with your speed, scout a clean route home, grab, and take the shortest familiar route straight back to your plot. The egg is not safe until it sits in your hatch position.

• Stealing is the game's only official egg source: you take eggs from SCP monster guardians and carry them to your lab plot.
• The best egg is the one that makes it back to your plot — pick a target you can outrun, not the rarest-looking one.
• A clean run starts before you touch the egg and ends only when the new anomaly is working in your lab.
• Until the egg is inside your plot, it is not safe: do not stop to browse menus or other nests while carrying it.

The steal-and-return sequence, start to finish

Run the whole loop in this order:

Roadmap

1. 1

   Check your base

   Confirm there is an open egg and anomaly position before you leave.

2. 2

   Train if the gap is big

   Use the treadmill when the target's recommended speed is far above yours.

3. 3

   Pick a reachable egg

   Choose a target you can actually outrun rather than the rarest-looking one.

4. 4

   Steal and escape

   Grab it and immediately take the cleanest route home.

5. 5

   Deposit the egg

   Place it in the available hatch position.

6. 6

   Watch the timer

   Stay aware of the hatch timer and return when the egg is ready.

7. 7

   Hatch and place

   Hatch the egg, inspect the result, and place the new anomaly.

Steps 1–5 are the theft run itself: other players can ruin an open run, so the egg must reach the hatch position without pauses in shared areas. Steps 6–7 hand off to hatching once the egg is deposited.

Read the guard and choose a target you can escape with

Pause outside the guard's immediate area and answer three questions before touching the egg: what recommended speed is displayed nearby, can you see a clean route back toward your plot, and is the egg positioned where you can pick it up without wrestling it around obstacles?

Tips

Read the live label first

If the recommendation is far beyond your current speed, turn around — requirements rise sharply across the available guards, so trust the live label you see instead of a saved zone table.

Compare speed before grabbing

Choose an egg whose guard you can outrun, and compare the displayed recommendation with your current speed before going for the fanciest egg on screen.

Appearance is not a selection rule

Egg looks alone do not make a target safe: a shiny egg behind a speed wall is worth less than a normal egg you can carry home and hatch.

Fall back when outmatched

If your speed falls well short, go back to an earlier target and bring home an easier egg.

Scout the route before committing to the steal

Scout without an egg first: watch how far you must travel, where the route turns, and whether the target sits behind obstacles. A clean route can make a modest speed total more useful, while an awkward pickup can waste the advantage you trained. Check the area's recommended speed, trace a direct path back to your base, and decide how you will escape before grabbing. The beginner condensation is scout first, grab once, and head straight home; on the steal itself, choose a reachable egg and keep a direct route back to the lab while the guardian gives chase.

Prepare speed for one specific guard at a time

Your speed determines which egg runs are practical, so train for the next guard rather than forever: use the treadmill until the next guardian's displayed recommendation is a manageable risk.

Mechanic flow

1. 1

   Pick one guarded area

   Choose one guarded egg area to prepare for instead of training blindly.

2. 2

   Note the speed check

   Read that area's current recommended-speed label.

3. 3

   Train toward it

   Use the treadmill until your total speed is closer to that check.

4. 4

   Dry-run the route

   Run the route without carrying an egg if you need to learn the turns.

5. 5

   Steal when repeatable

   Attempt the theft only when the escape looks repeatable.

Move up only when the previous guard has become comfortably escapable. One lucky dodge does not mean the route is ready; train until you can repeat the escape without needing everything to go perfectly. Treadmill upgrade pricing and optional Robux multipliers are a separate training decision — for the egg run itself, only your resulting speed versus the live recommendation matters.

After the grab: the escape home

After the grab, point toward home and run. Turn toward your plot as soon as you pick up the egg: the moment after pickup is not the time to browse another nest, watch another player, or inspect the egg, because looking at other nests while a guard chases you is an easy way to lose the one you already have. A straight return reduces the time the guard has to close the gap, so take the shortest familiar route and avoid detours to other nests; once you carry it, prioritize control over exploration. Treat the chase as part of the run — recorded play shows guardians closing in during escapes, even where some references still describe the chase as community-reported, so trust what you see in your own session. Do not pause after pickup to inspect nearby eggs: turn toward home, keep the route direct, and deposit the egg before shopping or scouting again. At the plot, bring the egg to the available hatch location and deposit first; only then decide whether to train, shop for food, or scout another area. Do not start carrying a second objective while the first egg is still exposed or unplaced.

Keeping control of the carried egg and recovering a drop

The theft route stays dangerous after you pick up the target: other players, monster attacks, knockback, and narrow paths can all break control of the egg, and a guard can catch or knock you away even after you have picked it up. Knockback, pathing mistakes, and faster guards can separate you from the egg. If the egg drops, recover it before pushing farther — moving too far ahead without it can give another player time to claim it. Recorded runs show the recovery pattern working: after a guardian hit knocked the egg loose, the player found the egg on the ground nearby, grabbed it, and ran again. Do not stop to browse menus while carrying it.

Diagnosing a failing run: what each failure means

Match what you see mid-run to the fix:

Comparison

Comparison

What You Observe During A Run	Response
Recommendation is far above your speed	Return to the treadmill or choose an earlier target
The guard catches you immediately	Leave and train before retrying; add more training before testing again
You open a gap on straight ground but lose it on turns	Simplify the route, choose a straighter path, and stop detouring
The egg is awkwardly placed	Take a cleaner nearby target
Another player is contesting the egg	Avoid a long struggle; secure a different reachable egg
The guard no longer closes the gap	Attempt a normal egg delivery
The egg returns to its original position (teleports back) mid-attempt	Treat the attempt as failed and reassess speed and route

Recorded gameplay matches the worst rows: a player too slow to work a heavy egg down saw it teleport back, and another who tried a golden egg above their speed abandoned it because they were not fast enough.

Other players: contests, traps, and crowded servers

Egg runs get messy in a shared server. Use a route you know, grab the target, and head home instead of checking nearby nests; if another player is already moving the egg, do not assume they will leave it for you. One player lost an egg after moving it because someone else grabbed it, and recorded runs show the same risk mid-carry, including a player whose stolen egg was taken by someone else during the escape. Players also protect and contest eggs with placed traps — in one recorded run, a player kept tripping traps another player had set around the eggs; trap mechanics are not documented, so treat any traps you meet as something to observe and avoid rather than a system with known rules. With servers capped at five players, traffic around a popular crib can be the real hazard; during a crowded event window, complete one steal and leave rather than fighting the crowd.

When the same run keeps failing

If the same run keeps failing, change one thing: add some speed, then test again; if that does not help, try a cleaner path or skip an awkward egg, so you know what fixed the problem and stop feeding time into one bad setup. Stop forcing the run when repeated attempts end in knockback or the egg returning toward its original position — dragging an impossible target inch by inch proves nothing, and you need an egg at home. If a door, wall, or guardian stops you, train Speed before you blame the egg; if attempts fail repeatedly, return to the treadmill and improve the part of progression you can control. After a failed attempt, train for a bit or choose a closer target — aiming too far ahead wastes more time than almost anything else, because a high-zone egg does nothing for you if it teleports back or its guard catches you.

What recorded runs show about the steal itself

Recorded gameplay confirms how strict the speed gate is in practice. The steal can refuse below the label: one player mashing the grab prompt got a hard refusal and concluded more speed was needed, and a player just under a 50,000 recommendation could not steal either. Another treated the label as padded, attempted a 2.5 billion recommendation with 2 billion speed, failed, and concluded the recommendations were accurate after all. Guides describe the label as a practical warning for the area, but in observed play it behaves as an enforced gate — treat the displayed value as binding and recheck the current behavior in-game after updates. Guards do chase after pickup: players describe a guardian closing in while they outrun it, and one run outpaced the guardian Verity to steal one of her eggs. Heavy eggs add a second check: some large eggs must be worked (shimmed) down from their position, and a player without enough speed to finish the maneuver saw the egg teleport back.