Online 66.51.99.64:28035 checked 5m ago
Test
Connect
srv = rust.server("66.51.99.64:28036")
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 17 Sep. 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 65% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 20h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 20h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 20h | Thu 3 Dec, 19:00 UTC | FW 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, 17:57 UTC FW27d ago | 1 | NaN | running | 0 |
| 1 | Thu 1 Oct, 04:17 UTC27d ago | 1 | NaN | 0.6 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
5000 · seed 1337
- map
- Custom Map
- size
- 5000
- seed
- 1337
Server
srv.info()- address
- 66.51.99.64:28035
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 1 Oct 2026, 17:57 UTC
- hostname
- –
- first seen
- 13 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 91 on average | 67/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 9/1000 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 76 on average | 124/700 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 69 on average | 86/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 22.10 | EU · groups of 16+ · monthly · 67 on average | 7/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 60 on average | 273/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Test rank?
Over the last seven days Test sits at #14,528 on player hours, in the top 65% of ranked servers.
How full does Test run?
The sample now reads 0 players for Test, out of 50 slots. Over the last seven days it averaged 0 players and peaked at 1.
Server data
How smoothly does Test run?
The 48-hour average is 5 server fps, with a low of 5. Buildings, deployables and all else in the world took the count as high as 125,051 entities. Memory peaked at 6,722 MB. What players call lag is these two fields together: low fps and a rising entity count.
What Rust version does Test run?
Version Rust network protocol 2635 and build 168909 on Linux is reported by Test. The protocol has to match before you can join, and Steam does the updating.
Is Test up, and what does its uptime show?
Online is the state at the latest refresh for Test. The uptime it reports puts the last restart about 6 days ago. 168 of 168 hours up over the last 7 full days, or 100%. The first row Rust Data holds for it is dated 13 September 2026.
In which location is Test hosted?
No region is published by Test. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. 66.51.99.64:28035 is its address.
Map and rules
Which rules apply on Test, and what settings?
You will not find a gather rate in the string Test. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Oxide. VAC, Valve's anti-cheat, is enabled.
What is the map on Test?
The game generates the map on Test: procedural, size 5,000, seed 1337. Because size and seed determine the map, it can be viewed on RustMaps via this page. Under map name you will find: Custom Map.
Wipes and dates
When does Test wipe, and on what schedule?
A single wipe each month, the force wipe, is all Test does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 4 hours ago, and that is the one in play. Its tags carry a monthly wipe schedule.
On Test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. The crowd on the latest wipe topped out 1 hours after it began.
Tags and filters
Which lists on Rust Data hold Test, and which filters?
On Rust Data, Test appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on Test?
These tags are published by Test and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp50 (Max players): 50 slots in total; ts8 (Group limit): Unchanged from default, teams hold up to 8; 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): No region code is set; ^m (Monthly): Monthly: the wipe lands with Facepunch's force wipe; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): The Modded section lists it, because plugins or settings change the game. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Test?
In Rust, F1 opens the console: type client.connect 66.51.99.64:28035. Launch Rust on this page does the same by opening the game through Steam and connecting.