Mark Test Server
Offline 157.85.88.135:20387 checked 17h ago
Server instruments
last reading Wed 17:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 233 · below 20 is lag, below 10 is badEntities
48 h range 46,339–48,895 · memory 2,642 MBUptime
1 days 8 hours since its last restart, at the last readingPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 43% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Fri 16 Oct, 08:58 UTC13d ago | 1 | – | running | 0 |
| Wed 7 Oct, 10:48 UTC22d 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- 146/500
- 122/100
- 186/225
- 76/700
- 11/200
- 20/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on Mark Test Server?
At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in. Until the next wipe, the crowd stayed above half that peak in 0% of its recent wipes. When it didn't hold, by day 7 it fell below half.
What wipe timing does Mark Test Server follow?
The rhythm of Mark Test Server's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. 13 days 1 hours ago the current world was made.
Lists and filters
Which tags does Mark Test Server carry, and what do they mean?
Tags published by Mark Test Server, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Team cap of 8, which is the game default; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Which lists and filters on Rust Metrics show Mark Test Server?
Rust Metrics lists featuring Mark Test Server: Modded Rust servers, checked live. 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.
Occupancy
Where does Mark Test Server sit in the rankings?
Player hours over seven days put Mark Test Server at #9,459, in the top 43% of all ranked servers.
How full does Mark Test Server get?
Status for Mark Test Server: offline. Last seen 17 hours ago. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 14:00 UTC over the last 48 hours.
Operator and location
Where does Mark Test Server sit?
No region tag on Mark Test Server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 157.85.88.135:20387.
What Rust version is Mark Test Server on?
Version check: Rust network protocol 2635 and build 168909 on Linux, run by Mark Test Server. Matching protocol is required to join. Let Steam update your game.
How does Mark Test Server perform?
Over the last 48 hours the average was 239 server fps; the floor was 233. Peak entity count: 48,895. Buildings, deployables and all else included. Reading: 3,178 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.
Is Mark Test Server up, and how often does it stay up?
Check: connection. Mark Test Server is offline at this moment. Last contact was 17 hours ago. Check: restart. The uptime it reports puts the last restart about 32 hours ago. Uptime for the last 7 full days: 162 of 168 hours, or 96%. The first sighting on Rust Metrics was 7 October 2026.
Rules and settings
What settings and rules apply on Mark Test Server?
No gather rate appears in the name: Mark Test Server. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.
What map is Mark Test Server on?
Check: map. Procedural, size 3,000, seed 50000, generated by the game on Mark Test Server. View it on RustMaps from this page: matching size and seed give an identical map.
Join
How do you connect to Mark Test Server?
To join: start Rust, press F1 and type client.connect 157.85.88.135:20387. Or press Launch Rust here and Steam opens the game and connects you.