Rust StatisticsWorking papers on every public Rust server · 48,663 players now

Local PVE | Closed test

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 9d ago · 203.23.178.51:28015

Abstract

We describe the public Rust server Local PVE | Closed test, reached at 203.23.178.51:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #15,308 of all servers, the top 70%. It last wiped 9d ago.

Keywordsmodded oxide pve

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/40% full
In the queue0no queue
Seven-day mean0peak –
Rank2#15,308top 70%
Last wipe9d 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.

4Rank

The server stands in the top 70% 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
15k10k15k20k21 Sep25 Sep13 Oct17 Oct22 Oct26 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 gap6.8 daysbetween real wipes
Wipe-day peak0players, last three wipes
Mon 19 OctMon 12 Oct
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
Mon 19 Oct, 10:249d ago 0 – running 1
Mon 12 Oct, 14:4116d ago 1 – 6.8 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

No map picture published
Figure 5: The map: Procedural Map.
Table 4: The server's published settings.
Address203.23.178.51:28015
Region–
Max players4
Group limit8, the default
Wipe schedule–
Last wipe19 Oct 2026, 10:24 UTC
Hostname–
First seen21 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 browse modded Rust servers [2], rust pve servers [3] and servers wiping soon [4].

Table 5: Similar servers: the same kind of game, then region, group limit, rate and wipes.
ServerPlayers
[US] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoNA · no group limit · biweekly · 253 on average105/2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 242 on average129/2000
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 106 on average39/200
【炮炮PVE启蒙】纯净|特色|突袭|技能EA · groups of 16+ · biweekly · 58 on average64/200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 54 on average25/300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 50 on average40/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1What location does Local PVE | Closed test have?

A region is not published by Local PVE | Closed test. The location displayed by Rust Statistics is the server's own claim, not a lookup of where the machine stands. 203.23.178.51:28015 is its address.

A.2What is the reliability of Local PVE | Closed test, and is it online?

Local PVE | Closed test is currently offline, with the last sighting 9 days 21 hours ago. Of the 168 hours in the last 7 full days, 0 were served, an availability of 0%. Its first appearance in Rust Statistics's records is 21 September 2026.

A.3What version of Rust is run on Local PVE | Closed test?

Local PVE | Closed test is running Rust network protocol 2634 and build 167781 on the Windows operating system. To join, your game must use the same protocol; Steam handles the update for you.

Wipe schedule

A.4What schedule does Local PVE | Closed test follow for wipes?

The record of Local PVE | Closed test's wipes is not yet sufficient to establish 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. The current world has been running for 9 days 22 hours.

A.5What characterises wipe day on Local PVE | Closed test?

Across its recent wipes, the average peak population was 0 players. The peak on the latest wipe came 0 hours after it began.

Player count

A.6What is the rank of Local PVE | Closed test among Rust servers?

The seven-day player-hours ranking puts Local PVE | Closed test at #15,308, within the top 70% of ranked servers.

A.7How would you characterise the player activity on Local PVE | Closed test?

Local PVE | Closed test is not online now; 9 days 21 hours have passed since it was last seen.

Tags, lists

A.8What do the tags associated with Local PVE | Closed test signify?

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp4 (Max players): It offers 4 slots; ts8 (Group limit): 8 per team, the value the game sets by default; v2634 (Protocol): Joining requires the same game version: protocol 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): Networking runs on RakNet, the game's standard layer; $r? (Region code): No region code is set; ^p (PvE): The threat is the world, not other players; ^o (Oxide): Oxide (uMod), a plugin framework, runs on this server; ^z (Modded): The game is altered by plugins or settings, so it is listed as Modded, which Local PVE | Closed test publishes as its tags. 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 Local PVE | Closed test be found among the Rust Statistics lists and filters?

Modded Rust servers and Rust PvE servers: live list are the Rust Statistics lists that Local PVE | Closed test fits. These filters on the server list return it: Type: Modded; Game mode: PvE; Server tag: PvE ^p, Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Rules, settings, map

A.10What are the settings and rules that govern Local PVE | Closed test?

The name of Local PVE | Closed test states no gather rate. At 8 players, the group limit equals the game's default. The mode is pve, which means fighting other players is excluded. It appears under Modded in the browser: the game is changed by plugins or settings. The plugin count is Oxide. The server has VAC on, Valve's anti-cheat.

A.11On which map does Local PVE | Closed test take place?

On Local PVE | Closed test the terrain is procedural, built by the game itself.

Connection

A.12What steps are required to join Local PVE | Closed test?

Press F1 inside Rust to open the console and enter client.connect 203.23.178.51: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 mp4,ptrak,$r?,v2634,^p,gmrust,cs167781,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp4Max players. It offers 4 slots.
ts8Group limit. 8 per team, the value the game sets by default.
v2634Protocol. Joining requires the same game version: protocol 2634.
cs167781Build. The game build is 167781.
ptrakNetworking. Networking runs on RakNet, the game's standard layer.
$r?Region code. No region code is set.
Gameplay
^pPvE. The threat is the world, not other players.
Mods and access
^oOxide. Oxide (uMod), a plugin framework, runs on this server.
^zModded. The game is altered by plugins or settings, so it is listed as Modded.

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. Rust pve servers. ruststatistics.org/top-rust-pve-servers.
  4. [4]Rust Statistics. Servers wiping soon. ruststatistics.org/rust-servers-wiping-today-list.