Offline 81.0.246.242:28615 checked 4d ago
private server test
Connect
srv = rust.server("81.0.246.242:28616")
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 59% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 81.0.246.242:28615
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 22:53 UTC
- hostname
- –
- first seen
- 24 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 526 on average | 291/300 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 319 on average | 269/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 291 on average | 26/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 278 on average | 23/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 38/100 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 247 on average | 129/200 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does private server test rank?
Player hours over seven days put private server test at #13,096, in the top 59% of the ranked set.
How full does private server test run?
private server test returns no live count at this refresh, having last been seen 4 days 9 hours ago. Over the last seven days it averaged 0 players and peaked at 1.
Server data
Which Rust version is private server test on?
Rust network protocol 2635 and build 168909 on Windows is what private server test runs. Steam updates your game for you, but the protocol must match to join.
Is private server test up, and what does its uptime show?
The latest sample has private server test offline, with a last sighting 4 days 9 hours ago. Over the last 4 full days the hours up number 0 of 96, 0%. Its earliest recorded date in Rust Data is 24 October 2026.
Where does private server test sit?
There is no region published for private server test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 81.0.246.242:28615.
Rules, settings, map
Which settings and rules does private server test run?
No gather rate appears in the name: private server test. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Community is its browser category. The description says vanilla, which here means facepunch's stock game, with rates, kits and rules untouched. Joining requires Rust's premium status. VAC, Valve's anti-cheat, is enabled.
What is the map on private server test?
private server test runs a procedural map, which the game generates.
Wipes and dates
On what schedule does private server test wipe?
A rhythm cannot be read from the wipes of private server test 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. A new world was started 4 days 9 hours ago, and that is the one in play.
Lists and tags
Which lists on Rust Data hold private server test, and which filters?
The Rust Data lists that private server test fits are: Rust community servers, unfiltered and Vanilla Rust servers. It appears under these filters on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Game mode: Premium; Server tag: Vanilla ^v and Premium ^q; Group limit: 5 or more; Last wipe: In the last week.
Which meanings do the tags on private server test hold?
These tags are published by private server test and read by the game's server browser: gmvanilla (Game mode): Game mode: vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^q (Premium): Joining requires Rust's premium status. 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 to join private server test?
In Rust, F1 opens the console: type client.connect 81.0.246.242:28615. Launch Rust on this page does the same by opening the game through Steam and connecting. Joining requires Rust's premium status.