Offline 193.29.139.147:28524 checked 35d ago
terrain recheck
Connect
srv = rust.server("193.29.139.147:28525")
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. 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 60% 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 1, 0 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 24 Sep, 16:50 UTC35d ago | 1 | NaN | running | 0 |
| 1 | Wed 23 Sep, 13:35 UTC36d ago | 1 | NaN | 1.1 days | 0 |
| 2 | Tue 22 Sep, 07:49 UTC37d ago | 1 | NaN | 1.2 days | 0 |
| 3 | Wed 16 Sep, 15:29 UTC43d ago | 0 | NaN | 5.7 days | 4 |
| 4 | Wed 16 Sep, 09:23 UTC43d ago | 4 | NaN | 0.3 days | 1 |
| 5 | Tue 15 Sep, 18:23 UTC44d ago | 4 | NaN | 0.6 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
- map
- Custom Map
- size
- –
- seed
- –
Server
srv.info()- address
- 193.29.139.147:28524
- region
- –
- max players
- 4
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Sep 2026, 16:50 UTC
- hostname
- –
- first seen
- 15 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 · 150 on average | 60/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 124/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 99/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 33/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 92 on average | 113/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 344/350 |
Quick answers
From the figures on this page.
Population
What position does terrain recheck take in the server rankings?
Rank #13,424 on seven-day player hours for terrain recheck, within the top 60% of all ranked servers.
What population does terrain recheck carry?
The current row shows terrain recheck offline; the last response was 35 days 4 hours ago.
Server data
Which Rust version is terrain recheck on?
Rust network protocol 2633 and build 164530 on Linux is what terrain recheck runs. The protocol has to match before you can join, and Steam does the updating.
How reliable is terrain recheck, and is it up?
Offline now for terrain recheck, last seen 35 days 4 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 15 September 2026.
Which location does terrain recheck run from?
There is no region published for terrain recheck. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 193.29.139.147:28524 is its address.
Settings and map
Which settings and rules does terrain recheck run?
No gather rate appears in the name: terrain recheck. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Carbon. VAC is not running; Valve's anti-cheat is off.
Wipe data
On what schedule does terrain recheck wipe?
Irregular wipe times on terrain recheck leave no next wipe to forecast. 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 35 days 4 hours ago, and that is the one in play.
On terrain recheck, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 0 hours after it began.
Tags and filters
Which lists on Rust Data hold terrain recheck, and which filters?
The Rust Data lists that terrain recheck fits are: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.
How should you read the server tags on terrain recheck?
Read by the game's server browser, the tags terrain recheck publishes are: gmrust (Game mode): Rust survival in its standard form; mp4 (Max players): The server lists 4 slots; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2633 (Protocol): Protocol 2633 is required; a different game version cannot connect; cs164530 (Build): The server runs build 164530; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): The plugin framework in use is Carbon. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way into terrain recheck?
Enter client.connect 193.29.139.147:28524 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.