Offline 193.141.60.251:28017 checked 27d ago
Test Rust
Connect
srv = rust.server("193.141.60.251:28018")
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 best
Top 60% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. 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, 1 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 20:56 UTC FW27d ago | 1 | NaN | running | 0 |
| 1 | Mon 28 Sep, 09:43 UTC31d ago | 0 | NaN | 3.5 days | 0 |
# 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
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 193.141.60.251:28017
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 20:56 UTC
- hostname
- –
- first seen
- 28 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 | ABYSS | PvE | US | Vanilla | Noob Friendly | NA · groups of 8+ · monthly · 55 on average | 28/200 |
| 1 | [EU] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | EU · groups of 8+ · monthly · 31 on average | 37/200 |
| 2 | [US] RustEZ Pure PvE | Low Decay | No Killing | No Raiding | NA · groups of 8+ · monthly · 31 on average | 20/200 |
| 3 | [PvE] Skyline PvE - No Raiding/Killing, No Decay, Noob Friendly | groups of 8+ · monthly · 22 on average | 12/150 |
| 4 | 【云梦泽PVE】萌新学习|土味养老|死亡不掉|原倍 | EA · groups of 30+ · monthly · 22 on average | 12/200 |
| 5 | JP RustPvE kokuu Server No kill No raid beeginner | EA · groups of 8+ · monthly · 15 on average | 5/200 |
Quick answers
From the figures on this page.
Population
What position does Test Rust take in the server rankings?
Player hours over seven days put Test Rust at #13,894, in the top 60% of the ranked set.
How full does Test Rust run?
Test Rust returns no live count at this refresh, having last been seen 27 days 20 hours ago.
Server facts
Which Rust version is Test Rust on?
Version Rust network protocol 2633 and build 165217 on Linux is reported by Test Rust. Joining needs the same protocol on your game; Steam handles the update.
How reliable is Test Rust, and is it up?
Test Rust is offline at this refresh; the last response came 27 days 20 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 28 September 2026.
Which location does Test Rust run from?
There is no region published for Test Rust. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 193.141.60.251:28017.
Settings and map
What rules and settings are recorded for Test Rust?
You will not find a gather rate in the string Test Rust. The group limit sits at the default of 8 players. Recorded as pve, no combat between players. The server browser lists it under Community. Anti-cheat status: VAC on.
What is the map on Test Rust?
A procedural map runs on Test Rust, generated by the game.
Wipes and dates
When does Test Rust wipe, and how often?
A rhythm cannot be read from the wipes of Test Rust on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 22 hours ago.
What is wipe day on Test Rust like?
Across recent wipes the busiest point averaged 0 players. 1 hours after the latest wipe, the crowd reached its peak.
Tags and filters
Where does Test Rust appear among Rust Data lists and filters?
The Rust Data lists that Test Rust fits are: Rust community servers, unfiltered and Rust PvE servers. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Game mode: PvE; Server tag: PvE ^p; Group limit: 5 or more.
Which meanings do the tags on Test Rust hold?
These tags are published by Test Rust and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts8 (Group limit): The default cap applies: 8 per team; v2633 (Protocol): The server speaks protocol 2633, so match your game version; cs165217 (Build): The server runs build 165217; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^p (PvE): Players do not fight each other here; the world supplies the danger. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
How can I connect to Test Rust?
In Rust, F1 opens the console: type client.connect 193.141.60.251:28017. Launch Rust on this page does the same by opening the game through Steam and connecting.