Rust StatisticsWorking papers on every public Rust server · 92,510 players now

TEST SERVER

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 34d ago · 194.147.90.159:35000

Abstract

We describe the public Rust server TEST SERVER, reached at 194.147.90.159:35000. It is offline at the last check, against a seven-day mean of 01. It ranks #16,363 of all servers, the top 71%. It last wiped 37d 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/6000% full
In the queue0no queue
Seven-day mean0peak –
Rank2#16,363top 71%
Last wipe37d 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.

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, measured since 17 Sep.

4Rank

The server stands in the top 71% 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 Sep22 Sep25 Sep27 Sep30 Sep2 Oct
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.

Table 2: The server's wipe rhythm, from the wipes recorded.
MeasureValueNote
Usual gap3.7 daysbetween real wipes
Wipe-day peak2players, last three wipes
Crowd held0%else halves by day 1
Thu 17 SepSun 13 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 0, 0 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 17 Sep, 16:5341d ago 0 – running 0
Sun 13 Sep, 23:1045d ago 4 halved by day 1 3.7 d 2

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

Custom map, no picture published
Figure 5: The map: TEST MAP, size 6000, seed 1337.
Table 4: The server's published settings.
Address194.147.90.159:35000
Region–
Max players600
Group limit100000 max
Wipe schedule–
Last wipe22 Sep 2026, 02:13 UTC
Hostname–
First seen13 Sep 2026
MapTEST MAP
Size6000
Seed1337

7Similar servers

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

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
RustReborn.gg EU - Bedwars | AimTrain | Creative | Arena | FFAEU · no group limit · 727 on average1109/2000
R2 - Aim training / Matchmaking / Facechecks - RU MainEU · groups of 12+ · 219 on average435/525
RustGames.gg | Lucky Pillars - EU 1EU · groups of 100+ · 83 on average145/400
DOGFIGHT 2 | BATTLEFIELD/HELI/MINI/FFA/MM/AIMTRAINING/PVPgroups of 30+ · weekly · 69 on average162/250
R2 - Aim training / Matchmaking / Facechecks - EU MainEU · groups of 12+ · 37 on average75/400
[EU] BekerMelk's Bow Aim Training Server | AimTrain | ukNLDEU · no group limit · 30 on average41/125

Appendix AQuick answers

From the figures on this page.

Server details

A.1What is the location of TEST SERVER?

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. 194.147.90.159:35000 is its address.

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

TEST SERVER is currently offline, with the last sighting 34 days ago. Its uptime over the last full days (7 days) was 0%, with 0 of 168 hours online. Its first appearance in Rust Statistics's records is 13 September 2026.

A.3What is the Rust version for TEST SERVER?

Rust network protocol 2633 and build 165217 is the version that TEST SERVER runs, on Windows. To join, your game must use the same protocol; Steam handles the update for you.

Wipe timing

A.4What schedule does TEST SERVER follow for wipes?

There are not yet enough recorded wipes for TEST SERVER to reveal its rhythm. Wiping is compulsory for every Rust server at the monthly force wipe, the next of which is Thursday 5 November at 19:00 UTC. 37 days 13 hours have passed since the current world was generated.

A.5What characterises wipe day on TEST SERVER?

Recent wipes saw an average peak of 2 players. The peak on the latest wipe came 0 hours after it began. The crowd stayed above half its peak until the next wipe in 0% of recent wipes. If not, the population dropped below half by day 1.

Population

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

The seven-day player-hours ranking puts TEST SERVER at #16,363, within the top 71% of ranked servers.

A.7How would you characterise the player activity on TEST SERVER?

The last recorded sighting of TEST SERVER was 34 days ago; it is offline now.

Tags, lists

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

gmrust (Game mode): Survival on standard Rust rules; mp600 (Max players): It offers 600 slots; ts100000 (Group limit): Teams are capped at 100000; v2633 (Protocol): The game protocol is 2633; your client must match it to join; cs165217 (Build): Build 165217 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $rRU (Region code): The code RU identifies the server's region; ^e (Minigames): This server runs minigames such as arenas, Bedwars and parkour; ^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 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.9Where can TEST SERVER be found among the Rust Statistics lists and filters?

These Rust Statistics lists include TEST SERVER: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Minigames ^e, Modded ^z and Carbon ^y; Group limit: 5 or more.

Rules, settings, map

A.10Which settings and rules are in force on TEST SERVER?

The name of TEST SERVER states no gather rate. 100000 players is the cap on a group. minigames & battle royale is the game mode here; parkour, arenas, battle royale and Bedwars. 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.11On which map does TEST SERVER take place?

The game generates TEST SERVER's procedural map at size 6,000, from seed 1337. Equal size and seed yield an identical map, which this page offers to view on RustMaps. The name of the map is TEST MAP.

Connection

A.12What is the process for joining TEST SERVER?

Press F1 inside Rust to open the console and enter client.connect 194.147.90.159:35000. 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 mp600,ptrak,$rRU,v2633,^e,^z,^y,gmrust,cs165217,ts100000.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp600Max players. It offers 600 slots.
ts100000Group limit. Teams are capped at 100000.
v2633Protocol. The game protocol is 2633; your client must match it to join.
cs165217Build. Build 165217 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$rRURegion code. The code RU identifies the server's region.
Gameplay
^eMinigames. This server runs minigames such as arenas, Bedwars and parkour.
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. Browse modded Rust servers. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.