Rust StatisticsWorking papers on every public Rust server · 71,386 players now

MyServer (TEST)

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 11d ago · 45.139.27.96:28015

Abstract

We describe the public Rust server MyServer (TEST), reached at 45.139.27.96:28015. It is offline at the last check, against a seven-day mean of 01. It ranks #13,019 of all servers, the top 60%. It last wiped 11d 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 now1/1001% full
In the queue0no queue
Seven-day mean0peak –
Rank2#13,019top 60%
Last wipe11d 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 60% 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
15k10k15k20k16 Oct18 Oct19 Oct21 Oct22 Oct24 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
Wipe-day peak1players, last three wipes
No hourly players around its wipes yet.
Figure 4: The first 48 hours of its last wipes: players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Sat 17 Oct, 04:5211d ago 1 – running 1

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: Custom Map.
Table 4: The server's published settings.
Address45.139.27.96:28015
Region–
Max players100
Group limit10 max
Wipe schedule–
Last wipe17 Oct 2026, 04:52 UTC
Hostname–
First seen16 Oct 2026
MapCustom 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 servers by player count [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 · 247 on average240/2000
[EU] Brits PvE Worlds 2.0 | RUST MMORPG | Quests | Custom WeapoEU · no group limit · biweekly · 237 on average268/2000
Chrayntopia ♡ ︎PvE | RP | PvPNA · groups of 8+ · biweekly · 102 on average100/200
【炮炮PVE启蒙】纯净｜特色｜突袭｜技能EA · groups of 16+ · biweekly · 60 on average20/200
[PvE] Relic | No Killing | No Raiding | No Decay | Noob Friendlgroups of 30+ · monthly · 53 on average61/300
TRAVELER PVE [ДЛЯ НОВИЧКОВ] Wipe 16.10EU · groups of 30+ · biweekly · 51 on average40/100

Appendix AQuick answers

From the figures on this page.

About the server

A.1In which location is MyServer (TEST) based?

A region is not published by MyServer (TEST). Rust Statistics does not look up the machine's location; it shows where the server says it is. 45.139.27.96:28015 is its address.

A.2What is the online status and reliability of MyServer (TEST)?

At the present moment, MyServer (TEST) is offline; it was last seen 11 days 15 hours 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 16 October 2026.

A.3What version of Rust is run on MyServer (TEST)?

MyServer (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.4When are wipes carried out on MyServer (TEST)?

The record of MyServer (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. 11 days 16 hours have passed since the current world was generated.

A.5How would you describe wipe day on MyServer (TEST)?

Across its recent wipes, the average peak population was 1 players. The crowd reached its maximum 1 hours after the latest wipe.

Population

A.6What position does MyServer (TEST) occupy in the ranking of Rust servers?

Ranked by player hours across seven days, MyServer (TEST) holds #13,019, in the top 60% of all ranked servers.

A.7How would you characterise the player activity on MyServer (TEST)?

The last recorded sighting of MyServer (TEST) was 11 days 15 hours ago; it is offline now.

Tags and filters

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

The game's server browser reads gmvanilla (Game mode): This is survival in its vanilla form; mp100 (Max players): 100 slots are available; ts10 (Group limit): Teams are capped at 10; v2634 (Protocol): The game protocol is 2634; your client must match it to join; cs167781 (Build): Build 167781 is the one running; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code has not been set; ^p (PvE): There is no player combat; the world supplies the danger; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game, which MyServer (TEST) publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.9Where can MyServer (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 MyServer (TEST) fits. It appears under the following filters on the server list: 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.

Settings and map

A.10Under what rules and settings does MyServer (TEST) operate?

No gather rate appears in the name of MyServer (TEST). 10 players is the cap on a group. The mode is pve, which means players cannot fight each other. 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.

Connection

A.11What is the process for joining MyServer (TEST)?

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

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmvanillaGame mode. This is survival in its vanilla form.
mp100Max players. 100 slots are available.
ts10Group limit. Teams are capped at 10.
v2634Protocol. The game protocol is 2634; your client must match it to join.
cs167781Build. Build 167781 is the one running.
ptrakNetworking. The network layer is RakNet, standard for the game.
$r?Region code. A region code has not been set.
Gameplay
^pPvE. There is no player combat; the world supplies the danger.
Mods and access
^oOxide. The plugin framework in use is Oxide (uMod).
^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 servers by player count. 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.