Rust StatisticsWorking papers on every public Rust server · 93,889 players now

TESTSERVER

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 2m ago · 95.33.82.157:28015

Abstract

We describe the public Rust server TESTSERVER, reached at 95.33.82.157:28015. At the last check it held 0 of 2 places, against a seven-day mean of 01. It ranks #15,434 of all servers, the top 70%. It last wiped 5d ago.

Keywordsoxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now0/20% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,434top 70%
Last wipe5d agono schedule published
Next wipe3–too few wipes seen yet

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.

0123413:0513:3013:5014:1514:3515:00
Figure 1: Players on the server, UTC: (a) every five minutes, from the Steam server list; (b) hourly mean and peak; (c) daily mean and peak.

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).

measure
range
This server has not answered a direct query in the last 48 hours.
Figure 2: Server performance. 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.

4Rank

The server stands in the top 70% 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.

No rank history yet.
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

5Wipes

5.1Schedule: too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

5.2History

Table 2: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sat 21 Nov, 14:3328m ago – – running 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

No map picture published
Figure 4: The map: Procedural Map.
Table 3: The server's published settings.
Address95.33.82.157:28015
Region–
Max players2
Group limit8, the default
Wipe schedule–
Last wipe16 Nov 2026, 11:13 UTC
Hostname–
First seen21 Nov 2026
MapProcedural 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 player-run rust server list [2] and next Rust wipe times [3].

Table 4: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 402 on average584/600
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 295 on average595/600
Rusty Moose |US Monthly|NA · groups of 12+ · monthly · 274 on average152/200
Rustoria.co - EU LongEU · groups of 14+ · monthly · 244 on average253/250
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 233 on average59/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 230 on average717/750

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is TESTSERVER based?

A region is not published by TESTSERVER. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 95.33.82.157:28015.

A.2How reliable is TESTSERVER, and is it currently online?

TESTSERVER is online at this time. Its first appearance in Rust Statistics's records is 21 November 2026.

A.3What is the Rust version for TESTSERVER?

TESTSERVER is running Rust network protocol 2636 and build 127089 on the Linux operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.4When are wipes carried out on TESTSERVER?

The record of TESTSERVER's wipes is not yet sufficient to establish its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 3 December at 19:00 UTC. The current world has been running for 5 days 3 hours.

Player count

A.5What is the rank of TESTSERVER among Rust servers?

The seven-day player-hours ranking puts TESTSERVER at #15,434, within the top 70% of ranked servers.

A.6What is the population level of TESTSERVER?

At this moment 0 players are on TESTSERVER, which has 2 slots in total. Averaged across the last seven days, the population is 0 players.

Tags and filters

A.7What do the tags associated with TESTSERVER signify?

The game's server browser reads gmvanilla (Game mode): Survival on vanilla rules; mp2 (Max players): The slot count is 2; ts8 (Group limit): 8 per team, the value the game sets by default; v2636 (Protocol): The game protocol is 2636; your client must match it to join; cs127089-84fd9a97663 (Build): This server publishes no build number; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^o (Oxide): Plugins are handled by Oxide (uMod), which TESTSERVER publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.8Where can TESTSERVER be found among the Rust Statistics lists and filters?

The Rust Statistics lists that TESTSERVER fits are: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and Plugins, not modded; Server tag: Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Settings and map

A.9What are the settings and rules that govern TESTSERVER?

No gather rate appears in the name of TESTSERVER. No cap is given beyond the game's default of 8 players per group. survival is the game mode here; the standard mode, in which you gather, build and raid. Combat and raiding against other players are allowed. The server browser lists it under Community. Oxide plugins are running. VAC is active: that is Valve's anti-cheat.

A.10What map is in use on TESTSERVER?

The game generates the map on TESTSERVER; that format is procedural.

Connection

A.11What steps are required to join TESTSERVER?

Press F1 inside Rust to open the console and enter client.connect 95.33.82.157: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?,v2636,gmvanilla,cs127089-84fd9a97663,ts8,^o.

Table 5: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. Survival on vanilla rules.
mp2Max players. The slot count is 2.
ts8Group limit. 8 per team, the value the game sets by default.
v2636Protocol. The game protocol is 2636; your client must match it to join.
cs127089-84fd9a97663Build. This server publishes no build number.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.
Mods and access
^oOxide. Plugins are handled by Oxide (uMod).

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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.