Offline 121.164.99.77:28015 checked 12d ago
Don't Come in
Connect
srv = rust.server("121.164.99.77:28016")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")48 hours: hourly readings. 30 to 90 days: one point a day, with the day's average and lowest fps, most entities and most memory, measured since 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 2, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 10:42 UTC25d ago | 2 | NaN | running | 0 |
| 1 | Sun 27 Sep, 08:44 UTC30d ago | 3 | halved by day 1 | 5.1 days | 0 |
| 2 | Tue 22 Sep, 06:26 UTC36d ago | 2 | held half | 5.1 days | 1 |
# Peak: the most players in the first 48 hours. Crowd: whether every day of the wipe kept at least half that peak, or the day it fell below. A new world less than six hours after a wipe is a restart, not a wipe of its own.
display(srv.map, srv.info())Map
5000 · seed 481815201
- map
- Procedural Map
- size
- 5000
- seed
- 481815201
Server
srv.info()- address
- 121.164.99.77:28015
- region
- –
- max players
- 5
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 10:42 UTC
- hostname
- ^
- first seen
- 20 Sep 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 109/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 131/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 115 on average | 113/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 88 on average | 44/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 83 on average | 22/1000 |
Quick answers
From the figures on this page.
Population data
How does Don't Come in compare in the rankings?
Rank #15,164 on seven-day player hours for Don't Come in, within the top 70% of all ranked servers.
How full does Don't Come in run?
Don't Come in returns no live count at this refresh, having last been seen 12 days 17 hours ago.
About the server
What is the Rust version on Don't Come in?
Rust network protocol 2634 and build 166586 on Windows is what Don't Come in runs. Joining needs the same protocol on your game; Steam handles the update.
Is Don't Come in up, and what does its uptime show?
Offline now for Don't Come in, last seen 12 days 17 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Rust Data logged it first on 20 September 2026.
Where does Don't Come in sit?
There is no region published for Don't Come in. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 121.164.99.77:28015.
Map and rules
What rules and settings are recorded for Don't Come in?
You will not find a gather rate in the string Don't Come in. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. Modded is the browser category: plugins or settings alter the game. The plugin count is Oxide. Anti-cheat status: VAC on.
What is the map on Don't Come in?
Don't Come in runs a procedural map of size 5,000 with seed 481815201, generated by the game. The same size and seed produce the same map; this page links to RustMaps so it can be viewed.
Wipe data
When does Don't Come in wipe, and on what schedule?
No next wipe can be predicted for Don't Come in, which wipes at irregular times. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. A new world was started 25 days 20 hours ago, and that is the one in play.
On Don't Come in, what happens on wipe day?
The average peak over recent wipes is 2 players. Peak population on the latest wipe came 0 hours in. Half the peak or more was held to the next wipe in 50% of recent wipes. In the wipes where it did not hold, half was lost by day 1.
Lists and tags
Where does Don't Come in appear among Rust Data lists and filters?
These Rust Data lists include Don't Come in: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on Don't Come in hold?
The game's server browser reads these tags from Don't Come in: gmvanilla (Game mode): The mode is vanilla survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166586 (Build): The server runs build 166586; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way into Don't Come in?
In Rust, F1 opens the console: type client.connect 121.164.99.77:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.