Rust StatisticsWorking papers on every public Rust server · 34,855 players now

TestServer

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 7m ago · 103.236.54.209:28015

Abstract

We describe the public Rust server TestServer, reached at 103.236.54.209:28015. At the last check it held 0 of 1000 places, against a seven-day mean of 01. It ranks #15,358 of all servers, the top 69%. It last wiped 14d ago.

Keywordsrust server

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/10000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,358top 69%
Last wipe14d agono schedule published
Next wipe3–no rhythm it keeps

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.

AveragePeak
0123404:0013:0022:0007:0016:0002: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
010020030040004:0013:0022:0007:0016:0002:00
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, measured since 14 Oct.

4Rank

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

RankRank in region
15k10k15k20k20 Sep11 Oct15 Oct20 Oct24 Oct29 Oct
Figure 3: Daily rank, overall and in its region; the axis is inverted, so up is better.

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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap3.5 daysbetween real wipes
On rhythm33%of its recent wipes
Wipe-day peak0players, last three wipes
Fri 16 OctWed 14 OctSun 11 Oct
01234+0h+9h+19h+28h+38h+47h
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 16 Oct, 08:3612d ago 0 – running 0
Wed 14 Oct, 19:1514d ago 0 – 1.6 d 0
Sun 11 Oct, 08:1817d ago 0 – 3.5 d 0
Wed 16 Sep, 19:4142d ago 0 – 24.5 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

Map of TestServer
Figure 5: The map: Procedural Map, size 2300, seed 12345. Open on RustMaps.
Table 4: The server's published settings.
Address103.236.54.209:28015
Region–
Max players1000
Group limit8, the default
Wipe schedule–
Last wipe14 Oct 2026, 19:15 UTC
Hostname–
First seen14 Sep 2026
MapProcedural Map
Size2300
Seed12345

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust community servers listed [2] and predicted wipe schedule [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rusty Moose |EU Mondays|EU · groups of 12+ · weekly · 555 on average149/250
Rustoria.co - EU East LongEU · groups of 12+ · monthly · 319 on average104/200
Rusty Moose |EU Main|EU · groups of 12+ · weekly · 291 on average14/250
Rustoria.co - EU MainEU · groups of 16+ · weekly · 286 on average16/250
Rustafied.com - EU FridayEU · groups of 16+ · weekly · 274 on average12/100
Rustoria.co - EU East MediumEU · groups of 12+ · biweekly · 250 on average20/200

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of TestServer smooth?

Over the past 48 hours, it ran at an average of 242 server fps, with a low of 224. Its entity count reached a maximum of 22,207, including buildings, deployables and all other world objects. Memory use peaked at 2,912 MB. Players experience lag when fps is low and the entity count is rising.

A.2What location does TestServer have?

There is no region published for TestServer. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. 103.236.54.209:28015 is its address.

A.3What is the reliability of TestServer, and is it online?

TestServer is online at this time. It last restarted around 14 days 6 hours ago, according to its reported uptime. The server was up 99% of the time over the last 7 full days, 167 of 168 hours. The first record of it by Rust Statistics dates to 14 September 2026.

A.4What version of Rust is run on TestServer?

TestServer is running Rust network protocol 2633 and build 163794 on the Linux operating system. Steam updates your game for you, but you must be on the same protocol to join.

Wipe timing

A.5When are wipes carried out on TestServer?

With irregular wipe times, TestServer offers no next wipe to predict. 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 14 days 8 hours ago.

A.6What characterises wipe day on TestServer?

The average busiest point of recent wipes was 0 players. The crowd reached its maximum 0 hours after the latest wipe.

Player count

A.7What is the rank of TestServer among Rust servers?

The seven-day player-hours ranking puts TestServer at #15,358, within the top 69% of ranked servers.

A.8What is the population level of TestServer?

The current population of TestServer is 0, drawn from 1,000 slots. The mean population for the last seven days is 0.

Tags, lists

A.9How should the tags on TestServer be interpreted?

gmrust (Game mode): Survival on standard Rust rules; mp1000 (Max players): 1,000 slots are available; ts8 (Group limit): Teams are limited to 8, as the game defaults; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs163794 (Build): The game build is 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set: these are the tags TestServer publishes, and the server browser reads them. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can TestServer be found among the Rust Statistics lists and filters?

These Rust Statistics lists include TestServer: Rust community servers, measured. It appears under the following filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Rules, settings, map

A.11Under what rules and settings does TestServer operate?

The name of TestServer states no gather rate. The group cap is 8 players, which is the default in the game. Listed as survival, the game mode is gather, build and raid: the standard game. Fighting and raiding between players are both permitted. Community is its category in the server browser. The server has VAC on, Valve's anti-cheat.

A.12What is the map for TestServer?

Generated by the game from seed 12345, the procedural map on TestServer measures 2,300. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What is the process for joining TestServer?

Enter client.connect 103.236.54.209:28015 in the Rust console, reached by pressing F1 after starting the game. Or press Launch Rust and join here, which opens Rust through Steam and connects you.

Appendix BServer tags

What each of the server's tags means. Published as mp1000,ptrak,$r?,v2633,gmrust,cs163794,ts8.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp1000Max players. 1,000 slots are available.
ts8Group limit. Teams are limited to 8, as the game defaults.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs163794Build. The game build is 163794.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.

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. Rust community servers listed. ruststatistics.org/top-rust-community-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.