Offline 151.59.150.11:28015 checked 1d ago
Rust PvE - Test
Connect
srv = rust.server("151.59.150.11:28017")
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 27 Oct. 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 41% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
3500 · seed 1337
- map
- Procedural Map
- size
- 3500
- seed
- 1337
Server
srv.info()- address
- 151.59.150.11:28015
- region
- –
- max players
- 5
- group limit
- 5 max
- wipe schedule
- –
- last wipe
- 25 Oct 2026, 10:44 UTC
- hostname
- –
- first seen
- 27 Oct 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 | RETRO RUST #3 Х5|MAX 5|LOOT+|CRAFT GLOBAL 29.10 | EU · groups of 5 · weekly · 77 on average | 98/280 |
| 1 | SHELBY RUST Х5 MAX5 | LOOT+ | SHOP | FPS+ | WIPE 27.10 | EU · groups of 5 · 61 on average | 19/160 |
| 2 | Rustico 3 | groups of 5 · 9 on average | 7/100 |
| 3 | 红果十倍/10.26号新开/爆枪/新人入门 | EA · groups of 6 · weekly · 9 on average | 0/200 |
| 4 | РУССКИЙ ДЛЯ НОВИЧКОВ | MAX5 | 50%Upkeep 23.10 | EU · groups of 5 · weekly · 1 on average | 0/200 |
| 5 | Bustabar NA PvP - No Wipe - Raid Protection | NA · groups of 5 · 1 on average | 2/50 |
Quick answers
From the figures on this page.
Population data
How does Rust PvE - Test compare in the rankings?
Player hours over seven days put Rust PvE - Test at #9,052, in the top 41% of the ranked set.
How full does Rust PvE - Test run?
Rust PvE - Test returns no live count at this refresh, having last been seen 35 hours ago. Over the last seven days it averaged 0 players and peaked at 1. Peak hour in the last 48 hours: 23:00 UTC, mean 1 players.
About the server
How well does Rust PvE - Test perform?
Server fps over the last 48 hours averages 215; the floor is 115. The entity count peaked at 66,738, covering buildings, deployables and the rest of the world. Memory peaked at 1,960 MB. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
What is the Rust version on Rust PvE - Test?
The build is Rust network protocol 2635 and build 168909 on Windows, run by Rust PvE - Test. Steam updates your game for you, but the protocol must match to join.
How reliable is Rust PvE - Test, and is it up?
Offline now for Rust PvE - Test, last seen 35 hours ago. A restart about 9 hours ago is what its reported uptime implies. Uptime of 46% across the last 1 full day: 11 hours of 24. The first row Rust Data holds for it is dated 27 October 2026.
Which location does Rust PvE - Test run from?
There is no region published for Rust PvE - Test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 151.59.150.11:28015.
Map and rules
What rules and settings are recorded for Rust PvE - Test?
You will not find a gather rate in the string Rust PvE - Test. The cap on a group is 5 players. Recorded as survival, the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. It appears under Modded, where plugins or settings change how the game plays. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
Which map has Rust PvE - Test loaded?
Rust PvE - Test runs a procedural map of size 3,500 with seed 1337, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
When does Rust PvE - Test wipe, and on what schedule?
Too few wipes are on record for Rust PvE - Test to reveal its rhythm. 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 4 days 11 hours ago.
Lists and tags
Which lists on Rust Data hold Rust PvE - Test, and which filters?
These Rust Data lists include Rust PvE - Test: Modded Rust servers. Under these filters on the server list, it is listed: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on Rust PvE - Test?
These tags are published by Rust PvE - Test and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp5 (Max players): 5 slots in total; ts5 (Group limit): The team cap is 5; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Connecting
How can I connect to Rust PvE - Test?
Enter client.connect 151.59.150.11:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.