TestServer
ruststatistics.org · independent, not affiliated with Facepunch Studios
Offline · checked 18h ago · 73.34.19.41:28015
Abstract
We describe the public Rust server TestServer, reached at 73.34.19.41:28015. It is offline at the last check, against a seven-day mean of 1 and a peak of 11. It ranks #9,219 of all servers, the top 41%. It last wiped 1d ago.
Keywordsmodded oxide
1Summary statistics
2Population
Figure 1 follows the players on the server at three scales: every five minutes over two hours, the hourly mean and peak over 48 hours, and the daily mean and peak over 90 days. Dashed uprights mark its wipes.
3Performance
We query the server directly for its frame rate, entity count and memory4. Low frames per second and a climbing entity count are what players feel as lag (Figure 2).
4Rank
The server stands in the top 41% of all ranked servers. Rank is on player hours over the last seven days, and 1 is best; Figure 3 draws it day by day.
5Wipes
5.1Schedule: no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
| Measure | Value | Note |
|---|---|---|
| Usual gap | 4 days | between real wipes |
| On rhythm | 50% | of its recent wipes |
| Wipe-day peak | 1 | players, last three wipes |
| Crowd held | 100% | of its cycles kept half the crowd |
5.2History
| Wiped (UTC) | Peak | Crowd | Lasted | Before |
|---|---|---|---|---|
| Tue 27 Oct, 00:551d ago | – | – | running | 0 |
| Thu 8 Oct, 05:3919d ago | 1 | held half | 18.8 d | 1 |
| Sun 4 Oct, 02:3624d ago | 1 | held half | 4.1 d | 0 |
| Wed 30 Sep, 04:1028d ago | 0 | – | 3.9 d | 0 |
| Mon 28 Sep, 20:2129d ago | 1 | – | 1.3 d | 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. Before: players just before it wiped. A new world less than six hours after a wipe is a restart, not a wipe of its own.
6Map and settings
| 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 |
| Map | Procedural Map |
| Size | – |
| Seed | – |
7Similar servers
Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded Rust population table [2] and predicted wipe schedule [3].
| Server | Players |
|---|---|
| ShockRust | Blue | NoLimitno group limit · 159 on average | 42/500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average | 134/100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average | 53/225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average | 23/700 |
| RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average | 4/200 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average | 7/1000 |
Appendix AQuick answers
From the figures on this page.
About the server
A.1In which location is TestServer based?
There is no region published for TestServer. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 73.34.19.41:28015 is its address.
A.2What is the online status and reliability of TestServer?
Right now, TestServer is offline, and the last time it was seen was 18 hours ago. Of the 168 hours in the last 7 full days, 9 were served, an availability of 5%. It was first observed on 28 September 2026 by Rust Statistics.
A.3What version of Rust is run on TestServer?
TestServer is running Rust network protocol 2635 and build 168909 on the Windows operating system. Steam updates your game for you, but you must be on the same protocol to join.
Wipe schedule
A.4What schedule does TestServer follow for wipes?
No next wipe can be predicted for TestServer since its wipes occur at irregular intervals. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. The world currently in use was created 25 hours ago.
A.5What happens on TestServer when wipe day arrives?
The average busiest point of recent wipes was 1 players. The peak on the latest wipe came 0 hours after it began. The crowd stayed above half its peak until the next wipe in 100% of recent wipes.
Player count
A.6What is the rank of TestServer among Rust servers?
The seven-day player-hours ranking puts TestServer at #9,219, within the top 41% of ranked servers.
A.7At what level does TestServer operate in terms of players?
The last recorded sighting of TestServer was 18 hours ago; it is offline now. Over the last week the count averages 1 players and reaches 1 at its height. Of the last 48 hours, the peak hour falls at 06:00 UTC, with an average of 1 players.
Tags and filters
A.8How should the tags on TestServer be interpreted?
Tags from TestServer, read by the game's server browser, are gmrust (Game mode): Rust survival, in its standard form; mp2 (Max players): 2 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2635 (Protocol): Joining requires the same game version: protocol 2635; cs168909 (Build): Build 168909 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game. The tags also carry current players, queue length and world creation time, shown at the top of this page.
A.9Where can TestServer be found among the Rust Statistics lists and filters?
The Rust Statistics lists that TestServer fits are: Modded Rust servers. It appears under the following filters 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.
Settings and map
A.10Under what rules and settings does TestServer operate?
The name of TestServer states no gather rate. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; gathering, building and raiding, as the game is usually played. Players may raid and fight one another. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.
A.11What map is in use on TestServer?
The game generates the map on TestServer; that format is procedural.
Connection
A.12What steps are required to join TestServer?
Press F1 inside Rust to open the console and enter client.connect 73.34.19.41:28015. Alternatively, the Launch Rust and join control on this page launches the game via Steam and completes the connection.
Appendix BServer tags
What each of the server's tags means. Published as mp2,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.
| Tag | Meaning |
|---|---|
| Game | |
gmrust | Game mode. Rust survival, in its standard form. |
mp2 | Max players. 2 slots are available. |
ts8 | Group limit. Teams are limited to 8, as the game defaults. |
v2635 | Protocol. Joining requires the same game version: protocol 2635. |
cs168909 | Build. Build 168909 is the one running. |
ptrak | Networking. The network layer is RakNet, standard for the game. |
$r? | Region code. No region code is set. |
| Mods and access | |
^o | Oxide. Oxide (uMod), a plugin framework, runs on this server. |
^z | Modded. Modded listing: plugins or settings modify the game. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
References
- [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
- [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
- [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.