Rust Data LabData lab · live
Live readings Servers11,679 Players49,738 Populated3,164 Fresh wipes · 3h118 Sampled every 5 min

Element card · group Modded · atomic number 9,463, its rank

Mark Test Server

Offline 157.85.88.135:20387 checked 16h ago

moddedoxide
Join the experiment
Atomic mass · players now 0/ 1 0% full Room to join
7-day average0peak 1
Rank · atomic number#9,463top 43%
Last wipe12d agono schedule published
Next wipe–too few wipes seen yet
Result 01

Players

Method
Every five minutes for the last two hours, from the Steam server list; hourly average and peak over 48 hours; daily average and peak over 90 days. UTC. Dashed lines are its wipes and the force wipes.
Result
AveragePeak
00.250.50.75110:0016:0022:0005:0011:0017:00

Hourly average and peak, UTC.

Result 02

Server performance

Method
Asked of the server itself, hour by hour and day by day: its frame rate, the entities in its world and the memory it holds.
Result
010020030040010:0016:0022:0005:0011:0017:00

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. From asking the server directly; low fps and a climbing entity count mean lag.

Result 03

Rank

Result

daily · 1 is best

RankRank in region
15k10k15k20k7 Oct11 Oct16 Oct20 Oct25 Oct29 Oct

Top 43% of all ranked servers. Ranked on player hours over the last seven days.

Reaction kinetics

Wipe schedule

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.

usual gap8.9 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 7

The first 48 hours of its last wipes

Fri 16 OctWed 7 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

Reaction log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 16 Oct, 08:58 UTC13d ago 1 – running 0
Wed 7 Oct, 10:48 UTC21d ago 1 halved by day 7 8.9 days 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. A new world less than six hours after a wipe is a restart, not a wipe of its own.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1 Sh ShockRust | Bl… 115
    ShockRust | Blue | NoLimit no group limit · 149 on average 115/ 500
  2. 2 Ми МИНИ-КАРТА 2Х … 132
    МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 132/ 100
  3. 3 Re RETRO RUST #1 … 184
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 184/ 225
  4. 4 Ru 404 RUST 2Х|ДЛ… 57
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 57/ 700
  5. 5 Ru RustSpain.com … 6
    RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 6/ 200
  6. 6 Ru 404 RUST 2Х|ДЛ… 24
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 24/ 1,000

Quick answers

from the figures on this page

Map and rules

What map is in play on Mark Test Server?

A procedural map of size 3,000 with seed 50000 runs on Mark Test Server, generated by the game. You can view it on RustMaps from this page, since matching size and seed produce the same map.

What settings and rules apply on Mark Test Server?

Nothing in the name of Mark Test Server gives a gather rate. Eight players per group is the limit, the game's default. Play runs as survival, raiding, building and gathering: the standard game. You can fight other players and raid them. In the server browser it sits under Modded: the game is changed by plugins or settings. The plugin count is Oxide. The VAC anti-cheat from Valve is enabled.

Server details

In what location does Mark Test Server sit?

No region is published by Mark Test Server. Rust Data Lab shows a server's stated location, not a verified position of the machine. Connect at 157.85.88.135:20387.

On what Rust version does Mark Test Server operate?

Rust network protocol 2635 and build 168909 on Linux is what Mark Test Server uses. Your game needs to match the protocol to join, and Steam updates it automatically.

Does Mark Test Server stay up, and how reliable is its uptime?

Currently offline, Mark Test Server was last seen 16 hours ago. About 32 hours ago is when it last restarted, based on its uptime. For the last 7 full days, 162 of 168 hours were online, giving 96% uptime. On 7 October 2026, Rust Data Lab saw it for the first time.

How well does Mark Test Server perform?

Server fps averaged 239 over the last 48 hours, with 233 as the lowest. The maximum entity count was 48,895, covering buildings, deployables and all else in the world. The highest memory usage was 3,178 MB. Lag, as players feel it, is caused by low fps and an increasing entity count.

Wipes and resets

What is the wiping pattern on Mark Test Server?

Too few wipes are on record for Mark Test Server to reveal a rhythm. The monthly force wipe resets every Rust server; it next occurs on Thursday 5 November at 19:00 UTC. 12 days 23 hours ago the current world was made.

How does Mark Test Server look on the day of a wipe?

Averaged across its recent wipes, the busiest point drew 1 players. 1 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. Where it did not hold, the crowd dropped below half by day 7.

Lists and tags

What should you understand from the tags Mark Test Server carries?

The game's server browser reads the tags Mark Test Server publishes, which are gmrust (Game mode): Standard Rust survival is the game here; mp1 (Max players): It has 1 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): Protocol 2635 is required; join only if your game matches it; cs168909 (Build): Build number: 168909; ptrak (Networking): RakNet is the network layer here, as standard in Rust; $r? (Region code): No region code is set; ^o (Oxide): A plugin framework called Oxide (uMod) powers the plugins; ^z (Modded): You will find it under Modded: the game is altered by plugins or settings. The tags carry more as well: current players, the queue and when the world was made, all shown at the top of this page.

Where among the Rust Data Lab lists and filters does Mark Test Server come up?

The Rust Data Lab lists that include Mark Test Server are: Modded Rust servers, measured. Applying these filters on the server list returns it: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

What position does Mark Test Server hold among Rust servers?

The seven-day player-hours table has Mark Test Server at #9,463, in the top 43% of ranked servers.

What does the current player count on Mark Test Server tell you?

Mark Test Server is offline at the moment; the last sighting was 16 hours ago. A seven-day sample gives 0 players on average and 1 at the top. The busiest point in the last 48 hours came at 14:00 UTC, averaging 1 players.

How to join

How can you connect to Mark Test Server?

In Rust, press F1 and enter client.connect 157.85.88.135:20387. Or click Launch Rust here to open Rust via Steam and connect automatically.

Server tags

what each one means

Published as mp1,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode Standard Rust survival is the game here.
mp1
Max players It has 1 slots.
ts8
Group limit Teams cap at 8, which is the game default.
v2635
Protocol Protocol 2635 is required; join only if your game matches it.
cs168909
Build Build number: 168909.
ptrak
Networking RakNet is the network layer here, as standard in Rust.
$r?
Region code No region code is set.

Mods and access

^o
Oxide A plugin framework called Oxide (uMod) powers the plugins.
^z
Modded You will find it under Modded: the game is altered by plugins or settings.

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.