Rust StatisticsWorking papers on every public Rust server · 94,129 players now

Test Server

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 9m ago · 216.245.177.46:28015

Abstract

We describe the public Rust server Test Server, reached at 216.245.177.46:28015. At the last check it held 0 of 30 places, against a seven-day mean of 01. It ranks #15,344 of all servers, the top 69%. It last wiped 23d ago.

Keywordssolo

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/300% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,344top 69%
Last wipe23d 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
0123416:0001:0010:0020:0005:0014: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
05010015020016:0001:0010:0020:0005:0014: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 17 Sep.

4Rank

The server stands in the top 69% of all ranked servers, and #199 of the solo servers (top 90%). 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 Sep28 Sep6 Oct13 Oct21 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 gap10.7 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak1players, last three wipes
Crowd held50%else halves by day 2
Tue 6 OctThu 17 SepTue 15 Sep
00.250.50.751+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 1, 28 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Tue 6 Oct, 10:5323d ago 1 – running 0
Thu 17 Sep, 10:3942d ago 1 halved by day 2 19 d 0
Tue 15 Sep, 00:5744d ago 1 held half 2.4 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 Test Server
Figure 5: The map: Procedural Map, size 4000, seed 3513435846. Open on RustMaps.
Table 4: The server's published settings.
Address216.245.177.46:28015
Region–
Max players30
Group limitsolo
Wipe schedule–
Last wipe6 Oct 2026, 10:53 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4000
Seed3513435846

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are rust solo-only server list [2], player-run rust server list [3] and servers wiping soon [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
Rustafied.com - EU SoloEU · solo · weekly · 119 on average318/325
Rustafied.com - US SoloNA · solo · weekly · 104 on average20/100
RustForNoobs.com | Mondays | SOLO ONLY | EUEU · solo · weekly · 54 on average59/100
RustForNoobs.com | SOLO ONLY | Weekly | EUEU · solo · weekly · 48 on average21/100
Lone Wolf Rust | Solo Only, Monthly, Vanilla, No BP WipesNA · solo · monthly · 35 on average26/100
[JP][日本] Bocchi The Rust! |SOLO ONLY| 1人 ソロ用 10/23EA · solo · weekly · 35 on average8/100

Appendix AQuick answers

From the figures on this page.

Server details

A.1Does Test Server perform well?

Over the past 48 hours, it ran at an average of 96 server fps, with a low of 76. Buildings, deployables and all other world objects counted together reached a maximum of 88,251 entities. Memory use peaked at 5,624 MB. Players experience lag when fps is low and the entity count is rising.

A.2What location does Test Server have?

There is no region published for Test Server. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 216.245.177.46:28015.

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

Test Server is online at this time. Based on the uptime it reports, the last restart occurred about 15 hours ago. Its uptime over the last full days (7 days) was 99%, with 167 of 168 hours online. Its first appearance in Rust Statistics's records is 13 September 2026.

A.4What is the Rust version for Test Server?

Test Server is running Rust network protocol 2634 and build 166652 on the Windows operating system. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5When are wipes carried out on Test Server?

With irregular wipe times, Test Server 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 current world has been running for 23 days 4 hours.

A.6How would you describe wipe day on Test Server?

The average busiest point of recent wipes was 1 players. The peak on the latest wipe came 28 hours after it began. For 50% of recent wipes, the population did not fall below half the peak before the next wipe. If not, the population dropped below half by day 2.

Player count

A.7What position does Test Server occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Test Server at #15,344, within the top 69% of ranked servers. Within the solo group, its position is #199.

A.8How would you characterise the player activity on Test Server?

On Test Server, 0 of the 30 slots are occupied at present. Averaged across the last seven days, the population is 0 players.

Tags and filters

A.9What do the tags associated with Test Server signify?

gmrust (Game mode): Survival on standard Rust rules; mp30 (Max players): 30 slots are available; ts1 (Group limit): Teams are capped at 1; v2634 (Protocol): Your game must run protocol 2634 to connect; cs166652 (Build): The game build is 166652; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): No region code is set: these are the tags Test Server publishes, and the server browser reads them. Current players, queue and the world's creation time are among the tags as well, displayed at the top of this page.

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

These Rust Statistics lists include Test Server: Rust community servers, measured and Solo Rust servers. You will find it on the server list filtered by: Type: Community (not modded, not official) and No plugins at all; Group limit: Solo.

Rules, settings, map

A.11What are the settings and rules that govern Test Server?

No gather rate appears in the name of Test Server. No teams are allowed; solo is the only option. The mode is survival, which means gathering, building and raiding, as the game is usually played. Combat and raiding against other players are allowed. Community is its category in the server browser. The server has VAC on, Valve's anti-cheat.

A.12What is the map for Test Server?

The game generates Test Server's procedural map at size 4,000, from seed 3513435846. Because size and seed determine the map, RustMaps can show it, linked from this page.

Connection

A.13What is the process for joining Test Server?

Press F1 inside Rust to open the console and enter client.connect 216.245.177.46: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 mp30,ptrak,$r?,v2634,gmrust,cs166652,ts1.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp30Max players. 30 slots are available.
ts1Group limit. Teams are capped at 1.
v2634Protocol. Your game must run protocol 2634 to connect.
cs166652Build. The game build is 166652.
ptrakNetworking. RakNet is the network layer here, as it is by default in 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 solo-only server list. ruststatistics.org/top-solo-rust-servers.
  3. [3]Rust Statistics. Player-run rust server list. ruststatistics.org/top-rust-community-servers.
  4. [4]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.