Rust StatisticsWorking papers on every public Rust server · 51,299 players now

TEST

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 24d ago · 185.30.229.67:28015

Abstract

We describe the public Rust server TEST, reached at 185.30.229.67:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,191 of all servers, the top 58%. It last wiped 24d ago.

Keywordsmodded oxide

Access. Launch Rust and join ‹ all servers

1Summary statistics

Table 1: The server at the last check, its week and its standing.
MeasureValueNote
Players now1/1010% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,191top 58%
Last wipe24d 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.

No hourly history yet.
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 58% 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 Sep24 Sep29 Sep3 Oct7 Oct11 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 gap2.9 daysbetween real wipes
On rhythm20%of its recent wipes
Wipe-day peak2players, last three wipes
Crowd held100%of its cycles kept half the crowd
Sun 4 OctSat 3 OctFri 2 Oct
00.511.52+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 2, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sun 4 Oct, 12:1424d ago 2 – running 0
Sat 3 Oct, 17:4125d ago 2 – 0.8 d 1
Fri 2 Oct, 15:1526d ago 2 – 1.1 d 0
Tue 29 Sep, 17:1329d ago 2 held half 2.9 d 0
Fri 25 Sep, 23:0333d ago 2 held half 3.8 d 0
Mon 14 Sep, 18:5544d ago 2 held half 11.2 d 3

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 5: The map: Procedural Map.
Table 4: The server's published settings.
Address185.30.229.67:28015
Region–
Max players10
Group limit8, the default
Wipe schedule–
Last wipe4 Oct 2026, 12:43 UTC
Hostname–
First seen13 Sep 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 modded Rust population table [2], primitive rust servers [3] and predicted wipe schedule [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
RustForNoobs.com Primitive | Bow / Melee | MedievalNA · groups of 16+ · biweekly · 1 on average0/50
[US East] Facepunch Primitive 1NA · groups of 8+ · monthly · 21 on average33/400
[EU] Facepunch Primitive 1EU · groups of 8+ · monthly · 16 on average7/400
JumpRust.com - EU 3x|Primitive|Full PVP|Shop|Kits|TP|Clans|EU · groups of 16+ · 3x · biweekly · 5 on average8/120
JumpRust.com - US 3x|Primitive|Full PVP|Shop|Kits|TP|Clans|NA · groups of 16+ · 3x · biweekly · 4 on average7/120
Rust4Noobs | Solo/Duo | Primitive Monthly | No BP WipeEU · duo · monthly · 6 on average5/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is TEST based?

No region is published by TEST. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. You will find it at 185.30.229.67:28015.

A.2What is the reliability of TEST, and is it online?

TEST is currently offline, with the last sighting 24 days 9 hours ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. The first record of it by Rust Statistics dates to 13 September 2026.

A.3What is the Rust version for TEST?

The version of Rust on TEST is network protocol 2634 and build 166586, and the operating system is Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4What schedule does TEST follow for wipes?

Prediction of the next wipe is impossible for TEST, which wipes irregularly. 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 24 days 11 hours ago.

A.5What happens on TEST when wipe day arrives?

Recent wipes saw an average peak of 2 players. The crowd reached its maximum 0 hours after the latest wipe. For 100% of recent wipes, the population did not fall below half the peak before the next wipe.

Player count

A.6How does TEST compare with other Rust servers in the rankings?

The seven-day player-hours ranking puts TEST at #13,191, within the top 58% of ranked servers.

A.7What is the population level of TEST?

The last recorded sighting of TEST was 24 days 9 hours ago; it is offline now.

Tags and filters

A.8How should the tags on TEST be interpreted?

Tags from TEST, read by the game's server browser, are gmprimitive (Game mode): Guns are absent under primitive rules: bows, spears and melee only; mp10 (Max players): The slot count is 10; ts8 (Group limit): The team cap is 8, which is the game default; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs166586 (Build): This server runs game build 166586; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region code is unset; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): Modded listing: plugins or settings modify the game. Also in the tags: players now, the queue, and when the world was made; these appear at the top of this page.

A.9Where can TEST be found among the Rust Statistics lists and filters?

Modded Rust servers and Primitive Rust servers are the Rust Statistics lists that TEST fits. These filters on the server list return it: Type: Modded; Game mode: Primitive; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.10What are the settings and rules that govern TEST?

Its name carries no gather rate for TEST. No cap is given beyond the game's default of 8 players per group. Listed as primitive, the game mode is guns are absent: bows, spears and melee only. Combat and raiding against other players are allowed. Plugins or settings change the game; the browser files it under Modded. Plugins number Oxide on this server. VAC is active: that is Valve's anti-cheat.

A.11What map is in use on TEST?

A procedural map, generated by the game, is what TEST runs.

Connection

A.12How do you connect to TEST?

Enter client.connect 185.30.229.67: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 mp10,ptrak,$r?,v2634,gmprimitive,cs166586,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmprimitiveGame mode. Guns are absent under primitive rules: bows, spears and melee only.
mp10Max players. The slot count is 10.
ts8Group limit. The team cap is 8, which is the game default.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs166586Build. This server runs game build 166586.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. The region code is unset.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. 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. [1]Rust Statistics. The Rust server list. ruststatistics.org/rust-server-directory.
  2. [2]Rust Statistics. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Primitive rust servers. ruststatistics.org/top-primitive-rust-servers.
  4. [4]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.