Rust StatisticsWorking papers on every public Rust server · 42,340 players now

Test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 6m ago · 24.113.60.221:28015

Abstract

We describe the public Rust server Test, reached at 24.113.60.221:28015. At the last check it held 0 of 50 places, against a seven-day mean of 0 and a peak of 21. It ranks #7,675 of all servers, the top 34%. It last wiped 22h ago.

Keywordsmodded carbon

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/500% full
In the queue0no queue
Seven-day mean0peak 2, 48 h peak 2
Rank2#7,675top 34%
Last wipe22h 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.

AveragePeakWipe
00.511.5203:0007:0011:0015:0020:0000:00Wiped Wed 28 Oct, 03:08 UTCWIPE
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
Server fpsWipe
05010015020003:0007:0011:0015:0020:0000:00Wiped Wed 28 Oct, 03:08 UTCWIPE
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 27 Sep.

4Rank

The server stands in the top 34% 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
15k10k15k20k27 Sep3 Oct10 Oct16 Oct23 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 gap13 daysbetween real wipes
On rhythm0%of its recent wipes
Wipe-day peak4players, last three wipes
Crowd held50%else halves by day 8
Sun 11 OctFri 2 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 3, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Wed 28 Oct, 03:0822h ago – – running 0
Sun 11 Oct, 03:4917d ago 3 halved by day 8 17 d 3
Fri 2 Oct, 04:2726d ago 5 held half 9 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
Figure 5: The map: Procedural Map, size 4500, seed 62803. Open on RustMaps.
Table 4: The server's published settings.
Address24.113.60.221:28015
Region–
Max players50
Group limit8, the default
Wipe schedule–
Last wipe28 Oct 2026, 03:08 UTC
Hostname–
First seen27 Sep 2026
MapProcedural Map
Size4500
Seed62803

7Similar servers

Servers of the same kind of game, then region, group limit, rate and wipes. The lists this server belongs to are modded servers by player count [2] and next Rust wipe times [3].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
ShockRust | Blue | NoLimitno group limit · 155 on average32/500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10EU · groups of 8+ · weekly · 128 on average120/100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 117 on average34/225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 92 on average26/700
RustSpain.com | EU MainEU · groups of 12+ · weekly · 88 on average5/200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average4/1000

Appendix AQuick answers

From the figures on this page.

About the server

A.1Does Test perform well?

The server fps averaged 151 over the last 48 hours, never dropping below 113. Buildings, deployables and all other world objects counted together reached a maximum of 121,303 entities. The peak memory usage was 4,980 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2In which location is Test based?

A region is not published by Test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 24.113.60.221:28015 is its address.

A.3How reliable is Test, and is it currently online?

At the present moment, Test is online. The uptime it reports indicates a restart about 20 hours ago. The server was up 57% of the time over the last 7 full days, 95 of 168 hours. Its first appearance in Rust Statistics's records is 27 September 2026.

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

Rust network protocol 2635 and build 168909 is the version that Test runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.5When are wipes carried out on Test?

With irregular wipe times, Test offers no next wipe to predict. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. 22 hours have passed since the current world was generated.

A.6What happens on Test when wipe day arrives?

Across its recent wipes, the average peak population was 4 players. The crowd reached its maximum 0 hours after the latest wipe. For 50% of recent wipes, the population did not fall below half the peak before the next wipe. In the other cases, the population fell below half by day 8.

Player count

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

The seven-day player-hours ranking puts Test at #7,675, within the top 34% of ranked servers.

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

On Test, 0 of the 50 slots are occupied at present. Averaged over the last seven days: 0 players; the same period peaks at 2. The busiest hour of the last 48 is 05:00 UTC, averaging 2 players.

Tags, lists

A.9What is the meaning of the tags on Test?

gmrust (Game mode): Survival on standard Rust rules; mp50 (Max players): It offers 50 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded; ^y (Carbon): The plugin framework is Carbon: these are the tags Test 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 be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Test fits. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.

Settings and map

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

No gather rate appears in the name of Test. The group cap is 8 players, which is the default in the game. The mode is survival, which means gather, build and raid: the standard game. Fighting and raiding between players are both permitted. The server browser lists it as Modded, where plugins or settings alter the game. Carbon plugins are running. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on Test?

The game generates Test's procedural map at size 4,500, from seed 62803. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

How to join

A.13What is the process for joining Test?

Press F1 inside Rust to open the console and enter client.connect 24.113.60.221: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 mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp50Max players. It offers 50 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs168909Build. This server runs game build 168909.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. No region code is set.
Mods and access
^zModded. The game is altered by plugins or settings, so it is listed as Modded.
^yCarbon. The plugin framework is Carbon.

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. Modded servers by player count. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Next Rust wipe times. ruststatistics.org/rust-servers-wiping-today-list.