
10/1|Rusty|US|3X|LowPop|2Week|QuickSmelt|Events
North America
4/150
Last checked 3 m ago
Wiped 1 d ago
Procedural Map
Server admin? Sign in with Steam to claim this server.
68 ms · Chicago
Last checked 7 m ago
0 / 100 players
Procedural Map
3x Max 2 30 days live Avg ping 67.2 ms Avg jitter 2 ms Wipe halving: 2 days Wipe cycle 14 ±7 days
Server owner? Add discord.gg/yourcode to your server's name or map to show your Discord invite here.
Connect: 45.51.211.64:28015
First seen 02.09.2026
Last wipe: (1 d ago)
| Wiped | Days since previous |
|---|---|
| 21 | |
| 7 | |
| — |
Wipe timing behind this data is sometimes inferred rather than confirmed, so daily figures right around a wipe boundary can land on the wrong day. Accuracy improves over time as detection gets more precise.
Highest peak 2 Sep 16 · 02:33 UTC Median daily peak 1 (median of daily peaks, not average population)
Observed daily peak
31 full · 0 partial · 0 offline · 0 no data
Each line follows one wipe cycle from the moment it started, lined up by days since that wipe rather than by calendar date — so you can compare how well this server held onto its population after different resets, independent of when each one happened.
Welcome to Fuel Bandits 3x - West Coast Server
No Cheating: Immediate ban for using cheats, hacks, or exploitation. Fair play only. Respectful Community: No tolerance for harassment, racism, or toxic behavior. We're a community of survivors, not adversaries. Raiding: Conduct raids with purpose; griefing just to destroy is discouraged. Leave room for others to rebuild. Communication: Keep chat strategic and clean; profanity is part of the game, but hate speech isn't allowed. Resource Sharing: Encouraged for strategic alliances, fostering a vibrant community. Admin Decisions: Admins act when needed, with the final say in disputes. Appeals can be made through the server's forum or Discord.
rs0002a5i}=?5ds5pu&*rM0%nSc0%oku
| Checked | Status | Ping | Players |
|---|---|---|---|
| Online | 68 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 0 | |
| Offline | — | — | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 1 | |
| Online | 67 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 69 ms | 1 | |
| Online | 67 ms | 0 | |
| Online | 65 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 72 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 69 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 71 ms | 0 | |
| Online | 72 ms | 0 | |
| Online | 65 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 65 ms | 0 | |
| Online | 65 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 69 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 67 ms | 0 | |
| Online | 68 ms | 0 | |
| Online | 66 ms | 0 | |
| Online | 68 ms | 0 |

North America
4/150
Last checked 3 m ago
Wiped 1 d ago
Procedural Map

North America
Events|TP|BGrade|QSmelt
0/50
Last checked 5 m ago
Wiped 1 d ago
Procedural Map

North America
| GO BROWNS!
3/100
Last checked 2 m ago
Wiped 1 d ago
Procedural Map
A wipe resets a server's map and usually player progress too — bases, resources, and blueprints, unless the server keeps blueprints through wipes (shown here as "No BP wipe"). Most servers wipe on a regular schedule, often weekly.
Facepunch pushes a mandatory update on the first Thursday of each month that requires every Rust server to wipe, regardless of its own schedule — a "force wipe," distinct from a server's regular map wipe.
The "Next wipe" time above is extracted from the server's own published schedule. "High confidence" means the server stated an explicit date or time; "Predicted" means it's estimated from the server's typical cadence and isn't guaranteed.
Copy the server address above, open Rust's in-game console with F1, and run client.connect followed by the address — or connect directly through Steam's server browser using the same address.