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

Mark Test Server

Rust Statistics

ruststatistics.org · independent, not affiliated with Facepunch Studios

Offline · checked 17h ago · 157.85.88.135:20387

Abstract

We describe the public Rust server Mark Test Server, reached at 157.85.88.135:20387. It is offline at the last check, against a seven-day mean of 0 and a peak of 11. It ranks #9,459 of all servers, the top 43%. It last wiped 13d 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/10% full
In the queue0no queue
Seven-day mean0peak 1, 48 h peak 1
Rank2#9,459top 43%
Last wipe13d 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
00.250.50.75111:0017:0023:0005:0011:0017: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
010020030040011:0017:0023:0005:0011:0017: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 7 Oct.

4Rank

The server stands in the top 43% 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
15k10k15k20k7 Oct11 Oct16 Oct20 Oct25 Oct29 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 gap8.9 daysbetween real wipes
Wipe-day peak1players, last three wipes
Crowd held0%else halves by day 7
Fri 16 OctWed 7 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 1, 1 hours in.

5.2History

Table 3: Every wipe recorded, newest first.
Wiped (UTC)PeakCrowdLastedBefore
Fri 16 Oct, 08:5813d ago 1 – running 0
Wed 7 Oct, 10:4821d ago 1 halved by day 7 8.9 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 Mark Test Server
Figure 5: The map: Procedural Map, size 3000, seed 50000. Open on RustMaps.
Table 4: The server's published settings.
Address157.85.88.135:20387
Region–
Max players1
Group limit8, the default
Wipe schedule–
Last wipe16 Oct 2026, 09:36 UTC
Hostname–
First seen7 Oct 2026
MapProcedural Map
Size3000
Seed50000

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 predicted wipe schedule [3].

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

Appendix AQuick answers

From the figures on this page.

About the server

A.1Is the performance of Mark Test Server smooth?

Its average server fps over the last 48 hours was 239, with a minimum of 233. The highest number of entities it carried was 48,895, comprising buildings, deployables and all other objects. Memory use peaked at 3,178 MB. Players experience lag when fps is low and the entity count is rising.

A.2What is the location of Mark Test Server?

There is no region published for Mark Test Server. Where a server says it is: that is what Rust Statistics shows, without looking up where the machine stands. You will find it at 157.85.88.135:20387.

A.3What is the reliability of Mark Test Server, and is it online?

Mark Test Server is currently offline, with the last sighting 17 hours ago. The uptime it reports indicates a restart about 32 hours ago. The server was up 96% of the time over the last 7 full days, 162 of 168 hours. Its first appearance in Rust Statistics's records is 7 October 2026.

A.4What is the Rust version for Mark Test Server?

Rust network protocol 2635 and build 168909 is the version that Mark Test Server runs, on Linux. Joining requires your game to be on the same protocol, and Steam updates it automatically.

Wipe timing

A.5On what cycle does Mark Test Server wipe?

The record of Mark Test Server's wipes is not yet sufficient to establish its rhythm. The monthly force wipe takes place on Thursday 5 November at 19:00 UTC and clears all Rust servers. The current world has been running for 13 days.

A.6What characterises wipe day on Mark Test Server?

Recent wipes saw an average peak of 1 players. The crowd reached its maximum 1 hours after the latest wipe. Half the peak was sustained until the next wipe in 0% of recent wipes. Otherwise, a fall below half took place by day 7.

Population

A.7What position does Mark Test Server occupy in the ranking of Rust servers?

The seven-day player-hours ranking puts Mark Test Server at #9,459, within the top 43% of ranked servers.

A.8What is the population level of Mark Test Server?

At this moment Mark Test Server is offline, having last been seen 17 hours ago. The peak over seven days is 1, against an average of 0. The busiest hour of the last 48 is 14:00 UTC, averaging 1 players.

Tags and filters

A.9What do the tags associated with Mark Test Server signify?

Tags from Mark Test Server, read by the game's server browser, are gmrust (Game mode): Survival on standard Rust rules; mp1 (Max players): The slot count is 1; ts8 (Group limit): 8 per team, the value the game sets by default; v2635 (Protocol): Your game must run protocol 2635 to connect; cs168909 (Build): Build 168909 is the one running; 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): The plugin framework in use is Oxide (uMod); ^z (Modded): Modded listing: plugins or settings modify the game. The tags also carry current players, queue length and world creation time, shown at the top of this page.

A.10Where can Mark Test Server be found among the Rust Statistics lists and filters?

Modded Rust servers are the Rust Statistics lists that Mark Test Server fits. You will find it on the server list filtered by: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Settings and map

A.11Under what rules and settings does Mark Test Server operate?

No gather rate appears in the name of Mark Test Server. At 8 players, the group limit equals the game's default. Listed as survival, the game mode is the standard mode, in which you gather, build and raid. Fighting and raiding between players are both permitted. It appears under Modded in the browser: the game is changed by plugins or settings. Oxide plugins are running. The server has VAC on, Valve's anti-cheat.

A.12What map is in use on Mark Test Server?

The game generates Mark Test Server's procedural map at size 3,000, from seed 50000. Size and seed being equal, the map is the same, so it can be viewed on RustMaps from this page.

Connection

A.13How do you connect to Mark Test Server?

Press F1 inside Rust to open the console and enter client.connect 157.85.88.135:20387. 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 mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z.

Table 6: The server's tags and their meanings.
TagMeaning
Game
gmrustGame mode. Survival on standard Rust rules.
mp1Max players. The slot count is 1.
ts8Group limit. 8 per team, the value the game sets by default.
v2635Protocol. Your game must run protocol 2635 to connect.
cs168909Build. Build 168909 is the one running.
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. 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 Rust population table. ruststatistics.org/top-modded-rust-servers.
  3. [3]Rust Statistics. Predicted wipe schedule. ruststatistics.org/rust-servers-wiping-today-list.