Rust StatisticsWorking papers on every public Rust server · 34,753 players now

myserver1

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Online · checked 11m ago · 157.85.86.75:23974

Abstract

We describe the public Rust server myserver1, reached at 157.85.86.75:23974. At the last check it held 0 of 4 places, against a seven-day mean of 0 and a peak of 21. It ranks #9,095 of all servers, the top 41%. It last wiped 26d 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 now0/40% full
In the queue0no queue
Seven-day mean0peak 2
Rank2#9,095top 41%
Last wipe26d 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.

AveragePeak
0123407:0016:0001:0010:0019:0004:00
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
05010015020007:0016:0001:0010:0019:0004:00
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 41% 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 Sep28 Sep5 Oct13 Oct20 Oct28 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 gap0.8 daysbetween real wipes
Wipe-day peak2players, last three wipes
Thu 1 OctThu 1 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, 2 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Thu 1 Oct, 20:40fw26d ago 2 – running 0
Thu 1 Oct, 01:3127d ago 2 – 0.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

Map of myserver1
Figure 5: The map: Procedural Map, size 4000, seed 1374978814. Open on RustMaps.
Table 4: The server's published settings.
Address157.85.86.75:23974
Region–
Max players4
Group limit8, the default
Wipe schedule–
Last wipe1 Oct 2026, 20:56 UTC
Hostname–
First seen13 Sep 2026
MapProcedural Map
Size4000
Seed1374978814

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] and Rust wipe forecast [3].

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

Appendix AQuick answers

From the figures on this page.

Server details

A.1Is the performance of myserver1 smooth?

Over the past 48 hours, it ran at an average of 106 server fps, with a low of 84. Buildings, deployables and all other world objects counted together reached a maximum of 90,259 entities. The peak memory usage was 5,772 MB. Lag, as players feel it, results from low fps combined with an increasing entity count.

A.2What location does myserver1 have?

A region is not published by myserver1. Rust Statistics does not look up the machine's location; it shows where the server says it is. You will find it at 157.85.86.75:23974.

A.3What is the online status and reliability of myserver1?

At the present moment, myserver1 is online. The uptime it reports indicates a restart about 4 days 9 hours ago. Its uptime over the last full days (7 days) was 100%, with 168 of 168 hours online. Its first appearance in Rust Statistics's records is 13 September 2026.

A.4What is the Rust version for myserver1?

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

Wipe timing

A.5When are wipes carried out on myserver1?

There are not yet enough recorded wipes for myserver1 to reveal its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The world currently in use was created 26 days 9 hours ago.

A.6What characterises wipe day on myserver1?

Recent wipes saw an average peak of 2 players. The peak on the latest wipe came 2 hours after it began.

Player count

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

Ranked by player hours across seven days, myserver1 holds #9,095, in the top 41% of all ranked servers.

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

The current population of myserver1 is 0, drawn from 4 slots. Over the last week the count averages 0 players and reaches 2 at its height.

Tags, lists

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

The game's server browser reads gmrust (Game mode): Survival on standard Rust rules; mp4 (Max players): The slot count is 4; ts8 (Group limit): The team cap is 8, which is the game default; v2635 (Protocol): The game protocol is 2635; your client must match it to join; cs167781 (Build): The game build is 167781; ptrak (Networking): RakNet is the network layer here, as it is by default in the game; $r? (Region code): A region code has not been set; ^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 myserver1 publishes as its tags. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can myserver1 be found among the Rust Statistics lists and filters?

These Rust Statistics lists include myserver1: Modded Rust servers. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Settings and map

A.11What are the settings and rules that govern myserver1?

Its name carries no gather rate for myserver1. No cap is given beyond the game's default of 8 players per group. The mode is survival, which means gathering, building and raiding, as the game is usually played. Players may raid and fight one another. Plugins or settings change the game; the browser files it under Modded. Oxide plugins are running. VAC, Valve's anti-cheat, is enabled.

A.12What is the map for myserver1?

Size 4,000 and seed 1374978814 define the procedural, game-generated map on myserver1. Because size and seed determine the map, RustMaps can show it, linked from this page.

How to join

A.13What is the process for joining myserver1?

Enter client.connect 157.85.86.75:23974 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 mp4,ptrak,$r?,v2635,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. The slot count is 4.
ts8Group limit. The team cap is 8, which is the game default.
v2635Protocol. The game protocol is 2635; your client must match it to join.
cs167781Build. The game build is 167781.
ptrakNetworking. RakNet is the network layer here, as it is by default in the game.
$r?Region code. A region code has not been set.
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. Modded Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Rust wipe forecast. ruststatistics.org/rust-servers-wiping-today-list.