Offline 73.34.19.41:28015 checked 1d ago
TestServer
Connect
srv = rust.server("73.34.19.41: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. 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 41% 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 | Tue 27 Oct, 00:55 UTC1d ago | NaN | NaN | running | 0 |
| 1 | Thu 8 Oct, 05:39 UTC20d ago | 1 | held half | 18.8 days | 1 |
| 2 | Sun 4 Oct, 02:36 UTC24d ago | 1 | held half | 4.1 days | 0 |
| 3 | Wed 30 Sep, 04:10 UTC28d ago | 0 | NaN | 3.9 days | 0 |
| 4 | Mon 28 Sep, 20:21 UTC29d ago | 1 | NaN | 1.3 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
- 73.34.19.41:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 02:53 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 | ShockRust | Blue | NoLimit | no group limit · 156 on average | 205/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 126/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 116 on average | 176/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 89 on average | 114/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 19/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 44/1000 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does TestServer rank?
Over the last seven days TestServer sits at #9,225 on player hours, in the top 41% of ranked servers.
How many players does TestServer hold at once?
Offline now for TestServer, with the last sample 30 hours ago. Over the last seven days it averaged 1 players and peaked at 1. The 48-hour sample puts the busiest hour at 06:00 UTC, averaging 1 players.
About the server
What is the Rust version on TestServer?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TestServer. The protocol has to match before you can join, and Steam does the updating.
How reliable is TestServer, and is it up?
TestServer is offline at this refresh; the last response came 30 hours ago. Over the last 7 full days the hours up number 9 of 168, 5%. Its earliest recorded date in Rust Data is 28 September 2026.
In which location is TestServer hosted?
For TestServer, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 73.34.19.41:28015.
Map and rules
Which settings and rules does TestServer run?
The name TestServer carries no gather rate. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Modded is the browser category: plugins or settings alter the game. Plugins installed: Oxide. Anti-cheat status: VAC on.
Which map has TestServer loaded?
The game generates its map: procedural, on TestServer.
Wipes and dates
On what schedule does TestServer wipe?
No next wipe can be predicted for TestServer, 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. The world it runs now was generated 37 hours ago.
What is wipe day on TestServer like?
The average peak over recent wipes is 1 players. The crowd on the latest wipe topped out 0 hours after it began. Recent wipes kept the crowd above half the peak until the next wipe 100% of the time.
Lists and tags
Which Rust Data filters and lists contain TestServer?
On Rust Data, TestServer appears in these lists: 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; Last wipe: In the last 3 days.
Which meanings do the tags on TestServer hold?
Read by the game's server browser, the tags TestServer publishes are: gmrust (Game mode): Rust survival in its standard form; mp2 (Max players): 2 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
How to join
What is the way into TestServer?
Enter client.connect 73.34.19.41:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.