Rust Code Raid List
The most common door lock codes players actually set — ranked from real leaked-PIN research — then 334 codes laid out in the order you should guess them, ready to copy.
The single most common 4-digit code — 10.713% of all codes on its own. Try it first, every time.
Share of all real-world codes covered by the top 20 below — 45 min of guessing at the lockout rate.
Guesses allowed before a 15-minute lockout — 32 attempts an hour, per raider.
Code raiding is the zero-boom raid: instead of blowing a door open you stand at the code lock and guess. It works for one reason — people are terrible at picking codes. Rust doesn't publish door-code statistics (no such dataset exists), but players punch in PINs the way humans do everywhere, and that has been studied hard. In DataGenetics' analysis of ~3.4 million leaked 4-digit PINs (Nick Berry), the twenty most popular codes accounted for 26.83% of everything people chose. One in four locks, openable from a list of twenty guesses.
The defender takeaway is the same list read upside down: if your code is on this page, change it before the next door-camper finds your base. See the base building guide for the rest of your defense.
The 20 most common 4-digit codes
| # | Code | Frequency |
|---|---|---|
| 1 | 1234 | 10.713% |
| 2 | 1111 | 6.016% |
| 3 | 0000 | 1.881% |
| 4 | 1212 | 1.197% |
| 5 | 7777 | 0.745% |
| 6 | 1004 | 0.616% |
| 7 | 2000 | 0.613% |
| 8 | 4444 | 0.526% |
| 9 | 2222 | 0.516% |
| 10 | 6969 | 0.512% |
| 11 | 9999 | 0.451% |
| 12 | 3333 | 0.419% |
| 13 | 5555 | 0.395% |
| 14 | 6666 | 0.391% |
| 15 | 1122 | 0.366% |
| 16 | 1313 | 0.304% |
| 17 | 8888 | 0.303% |
| 18 | 4321 | 0.293% |
| 19 | 2001 | 0.290% |
| 20 | 1010 | 0.285% |
Code frequencies from DataGenetics' analysis of ~3.4 million leaked 4-digit PINs — not a Rust-specific dataset (none exists), but the best public research on how people choose 4-digit codes. Together these 20 cover 26.83% of all PINs in the study.
The raid order — 334 codes, in the order to guess them
Numeric order is useless at a code lock — starting at 0000 and counting up would take 13 days. This is the same 4-digit space reordered by how likely a human is to have chosen it: the researched twenty first, then each pattern family expanded in full and deduped, so no code appears twice. Working straight down it takes 11 hours at the lockout rate.
Read this honestly: only Block 1 is ordered by measured frequency. Everything after it is a strategy ordering generated from the pattern families below — no per-code odds exist for those, so we don't print any. Anyone showing you a percentage next to code #147 invented it.
Block 1 — the researched top 20
#1–20measuredMeasured frequency, highest first. These twenty alone cover 26.83% of all real-world 4-digit codes.
Block 2 — remaining repeats & couplets
#21–106strategy orderRepeated pairs are 17.8% of all PINs and eight of the ten all-same codes are already above, so what's left of this family is the next-best value.
Block 3 — years
#107–190strategy orderRecent years first, then 19xx birth years newest-first. Every 19xx code sits in the most-used fifth of the dataset.
Block 4 — ladders & sequences
#191–227strategy orderRuns, reverse runs and doubled steps — the family 1234 belongs to.
Block 5 — keypad geometry
#228–257strategy orderLines, columns and corners traced on the number pad. 2580 — straight down the middle — ranks #22 overall.
Block 6 — day/month dates
#258–334strategy orderDDMM and MMDD birthdays. 1004 sits at #6 on measured frequency and reads exactly like this family — dates are how a lot of people pick four digits.
How long each block actually takes
Every figure here is arithmetic on one rule — 8 failed attempts, then a 15-minute lockout, so 32 guesses an hour per raider. Bring more raiders and it divides: the lockout is per-player, not per-lock.
| How far you go | Codes | Solo time | 4 raiders |
|---|---|---|---|
| Top 3 only (the drive-by check) | 3 | 15 min | 15 min |
| The researched top 20 | 20 | 45 min | 15 min |
| Blocks 1–2 (repeats & couplets) | 106 | 3.5 hours | 60 min |
| The full raid list above | 334 | 11 hours | 2.8 hours |
| Every possible code | 10,000 | 13 days | 3.3 days |
Derived from the 8-attempt / 15-minute rule only — no other assumptions. Doesn't count walking to the door, or the shock damage you take on every wrong entry.
Why those families — the patterns behind the order
Beyond the researched table, guesses follow human patterns. These are the families the blocks above are built from, in the order they tend to pay off — as strategy tiers, without made-up per-code odds.
Only ten codes and eight of them sit inside the researched top 20. The fastest tier to clear and the most likely to hit.
Sourced: 10 of these -20 codes appear in the top{n3} table above.
Repeated pairs are easy to type twice and easy to remember.
Sourced: Repeated-pair codes make up 17.8% of ALL PINs in the DataGenetics dataset.
Birth years and memorable dates. Recent years and 19xx birth years dominate.
Sourced: Every 19xx combination sits in the top fifth of the dataset; 2000 and 2001 are top-20.
Straight lines and corners on the numeric pad. People pick what their thumb can draw.
Sourced: 2580 — straight down the middle of a keypad — ranks #22 overall.
Ascending or descending runs and doubled steps. 1234 alone is >10% of all PINs; its cousins follow.
Sourced: 1234 (10.713%), 4321 and 1122 are all in the top 20.
Shock & lockout — the mechanics that limit code raiding
Failed guesses allowed on a code lock before that player is locked out.
How long you're locked out after 8 failed attempts — roughly 32 guesses per hour, per raider.
Craft cost of a Code Lock — 30s craft, no workbench, default blueprint. Datamined.
Every wrong entry also delivers an electric shock. Community wikis document the shock at roughly 5 damage, ramping up with rapid consecutive wrong entries and resetting after a short pause. This figure isn't in our datamine, so treat the exact number as community-documented rather than official.
Attempt limit and lockout: Facepunch — December 2021 update. Shock figure: Rust Wiki (community). Craft data from our datamine, verified Aug 2026.
Protect your base — how to pick a safe code
A good code is simply one that isn't human. Everything on this page is a blocklist:
- Nothing from the top-20 table or the pattern tiers — no repeats, couplets, years, keypad lines or sequences. That single rule removes the guesses that cover a quarter of all real-world codes.
- No birth years or anything a teammate could know. In the research, every 19xx code sat in the most-used fifth of the dataset.
- Pick four genuinely arbitrary digits and avoid "famous random" codes — 8068 was the rarest PIN in the 2012 study, and precisely because that was published, it isn't safe anymore.
- Change codes after every wipe and after kicking a teammate — guessing isn't the only way codes leak.
- Layer your doors. A random code makes a lock a 1-in-10,000 problem at 8 guesses per 15 minutes — at that point raiders reach for explosives instead, which is what your base design and raid cost are for.
Frequently Asked Questions
What are the most common Rust codes?expand_more
There's no Rust-specific dataset, but players pick codes the way humans pick PINs everywhere, and that IS well researched. In DataGenetics' analysis of ~3.4 million leaked 4-digit PINs, 1234 alone was 10.713% of all codes, followed by 1111 (6.016%) and 0000 (1.881%). The top 20 — mostly repeats like 7777, couplets like 1212 and years like 2000 — covered 26.83% of every PIN in the dataset.
How many tries do you get before a code lock locks you out?expand_more
8 failed attempts on any code lock triggers a 15-minute lockout for that player — added in Facepunch's December 2021 update. Each wrong entry also gives you an electric shock, so brute-forcing costs health as well as time.
How long does it take to code raid a door in Rust?expand_more
At 8 guesses per 15-minute lockout you get 32 guesses an hour per raider. The researched top 20 takes 45 min. The full 334-code raid list on this page takes 11 hours. Brute-forcing all 10,000 combinations solo would take 13 days of continuous guessing, which is why nobody does it.
Is code raiding still possible in Rust?expand_more
Yes, but it's slow by design. With 8 guesses per 15 minutes you get 32 guesses an hour, so clearing even the researched top-20 list takes 45 min per lock — and any random code is a 1-in-10,000 shot. Code raiding only really pays off against people who set codes from the top of this list.
Can you code raid in Rust Console Edition?expand_more
Code locks work the same way on console, and code raiding is possible there. On Console Edition community servers the failed-attempt limit and lockout cooldown are server-configurable settings, so how punishing it is depends on the server you're on.
Related guides
A real player's Rust raid guide: exact sulfur costs per structure, C4 vs rockets vs satchels vs eco raiding, online/offline tactics and defence.
A no-BS Rust base design guide: building tiers, upkeep, tool cupboards, bunkers, airlocks and honeycomb, plus the raid costs that actually matter.