Rust Server Analytics 52,558 players11,680 servers
All servers
Drill-through Server detail

Mark Test Server

Offline 157.85.88.135:20387 checked 16h ago

Drill-through
FilterServeris Mark Test Server
Attributes
moddedoxide
Last refreshed
Players now 0/ 1
7-day average 0 peak 1
Rank #9,463 top 43%
Last wipe 13d ago no schedule published
Next wipe – too few wipes seen yet
Capacity 0% full

Players

average and peak, with its wipes marked
AveragePeak
00.250.50.75110:0016:0022:0005:0011:0017:00

Hourly average and peak, UTC.

Server performance

fps, entities and memory, from asking the server directly
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.

Rank

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.

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.

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
ServerProfilePlayers now
ShockRust | Blue | NoLimit no group limit · 149 on average 132 / 500
МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 EU · groups of 8+ · weekly · 128 on average 122 / 100
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 EU · groups of 16+ · weekly · 118 on average 192 / 225
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 93 on average 71 / 700
RustSpain.com | EU Main EU · groups of 12+ · weekly · 88 on average 9 / 200
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 84 on average 21 / 1000

Quick answers

from the figures on this page

Wipe data

On what cycle does Mark Test Server wipe?

With too few of its wipes on record, Mark Test Server's rhythm is not yet clear. The monthly force wipe reaches every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. 13 days ago the current world was made.

On Mark Test Server, what happens on wipe day?

Recent wipes averaged a busiest count of 1 players. Peak population for the latest wipe came 1 hours after it began. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. By day 7 it had fallen below half where the hold failed.

Server details

What is the hosting location of Mark Test Server?

No region is published by Mark Test Server. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. You will find it at 157.85.88.135:20387.

What Rust build does Mark Test Server run?

The platform is Linux, with Rust network protocol 2635 and build 168909 running on Mark Test Server. Joining requires the same protocol on your game; Steam handles the update.

What uptime does Mark Test Server show, and is it up?

Offline at this refresh: Mark Test Server, last seen 16 hours ago. Its reported uptime indicates a restart roughly 32 hours ago. Uptime over the last full days (7) was 96%, or 162 of 168 hours. 7 October 2026 is when Rust Server Analytics first recorded it.

Is performance on Mark Test Server stable?

Server fps averaged 239 over the last 48 hours, with a floor of 233. Buildings, deployables and all other world objects brought the entity total to 48,895. Memory use reached 3,178 MB at peak. A climbing entity count and low fps are the lag players perceive.

Tags

How should the tags on Mark Test Server be read?

Tags from Mark Test Server, as read by the game's server browser, are: gmrust (Game mode): Survival in the standard Rust format; mp1 (Max players): 1 slots in total; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): No region code has been set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

Where does Mark Test Server appear across Rust Server Analytics's lists and filters?

Among the Rust Server Analytics lists Mark Test Server fits are: Modded Rust servers: live data. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Population

Against other Rust servers, how does Mark Test Server compare?

On player hours over seven days, Mark Test Server ranks #9,463, within the top 43% of ranked servers.

At what level does Mark Test Server run its population?

The last sighting of Mark Test Server was 16 hours ago; it is offline at this refresh. Averaging 0 players across seven days, the server reached a peak of 1. Averaged over 48 hours, activity is highest at 14:00 UTC with 1 players.

Settings

How is Mark Test Server configured, and what rules apply?

The name of Mark Test Server does not state a gather rate. The default group cap of 8 players applies. It runs survival, the standard game: gather, build, raid. Raiding and PvP combat are available. The Modded category lists it; plugins or settings change the game. Plugins from Oxide are in use. Anti-cheat status: VAC on.

The map on Mark Test Server: which one is it?

The game generates a procedural map of size 3,000 with seed 50000 for Mark Test Server. The map is reproducible from its size and seed and can be seen on RustMaps from here.

Connection

How do you connect to Mark Test Server?

In the Rust console (F1), enter client.connect 157.85.88.135:20387. Launch Rust on this page also works, opening Rust through Steam and connecting you.

Server tags

what each one means

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

Game

gmrust
Game mode Survival in the standard Rust format.
mp1
Max players 1 slots in total.
ts8
Group limit The game default applies: 8 per team at most.
v2635
Protocol Protocol 2635 is required: your game must match to connect.
cs168909
Build The game build is 168909.
ptrak
Networking It uses RakNet, the standard network layer for the game.
$r?
Region code No region code has been set.

Mods and access

^o
Oxide Plugin framework: Oxide (uMod).
^z
Modded Plugins or settings change the game, so it sits under 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.