RUST METRICSFlight deck · live data
Data live Servers11,751 Players55,890 Populated3,402 Fresh wipes 3 h132 Scan5 min
‹ All servers208.103.169.136:28010
Online Full Queue Fresh wipe Wipe due No query

[RD] TEST SERVER

Online 208.103.169.136:28010 checked 7m ago

quad monthly wipes moddedoxide
COM 1 · connect

Server instruments

last reading Wed 21:00 UTC
0 0.2 0.5 0.8 1 PAX 0 /?

Players now

no slots published 7-day avg7-day peak 1, past the slots
0 10 30 60 120 256 FPS 30 SERVER FPS

Server fps

48 h low 30 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 44,780 ×1000

Entities

48 h range 39,775–49,781 · memory 4,740 MB
1239 ET SINCE RESTART 1D 09H

Uptime

1 days 9 hours since its last restart, at the last reading
7-day average0peak 1
Rank#14,235top 64%
Last wipe26d agomonthly schedule
Next wipe7d 19hThu 5 Nov, 19:00 UTC FW
Memory4,740MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75111:0018:0000:0007:0013:0021:00

Hourly average and peak, UTC.

REC 2

Server performance

01020304011:0018:0000:0007:0013:0021: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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 64% of all ranked servers, and #588 of the quad servers (top 71%). Ranked on player hours over the last seven days.

PLAN

Wipe schedule

force wipes only

Next wipe Thursday 5 November, 19:00 UTC, in 7d 19h. The force wipe · high confidence

usual gap7.1 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4

Coming wipes

  1. WPT 1Thu 5 Nov, 19:00 UTC7d 19hFW
  2. WPT 2Thu 3 Dec, 19:00 UTC35d 19hFW

The first 48 hours of its last wipes

Fri 2 OctFri 25 Sep
00.250.50.751+0h+9h+19h+28h+38h+47h

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Fri 2 Oct, 15:31 UTC26d ago 1 – running 0
Fri 25 Sep, 13:59 UTC33d ago 1 halved by day 4 7.1 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe schedule

What happens on [RD] TEST SERVER when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 46 hours. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 4 it fell below half.

What wipe timing does [RD] TEST SERVER follow?

Once a month [RD] TEST SERVER wipes, with the force wipe. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. 26 days 7 hours ago the current world was made. A monthly wipe schedule is published in its tags.

Lists and filters

Which tags does [RD] TEST SERVER carry, and what do they mean?

Tags published by [RD] TEST SERVER, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): Slots: 0; ts4 (Group limit): Teams are capped at 4; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): The server runs game build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here; ^o (Oxide): It runs Oxide, also known as uMod; ^z (Modded): Plugins or settings make this a modded server; rustmaps (Custom tag): This tag is non-standard, added by the owner or a plugin. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does [RD] TEST SERVER appear in Rust Metrics lists and filters?

On Rust Metrics, [RD] TEST SERVER sits in these lists: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Monthly ^m, Modded ^z and Oxide ^o; Group limit: Quad; Wipe schedule: Monthly.

Player count

What position does [RD] TEST SERVER hold among Rust servers?

Player hours over seven days put [RD] TEST SERVER at #14,235, in the top 64% of all ranked servers. The quad group places it at #588.

What player count does [RD] TEST SERVER carry?

Reading for [RD] TEST SERVER: 0 players online now. Check: players over seven days. Average 0, peak 1. Average at the busiest hour was 1 players, at 19:00 UTC over the last 48 hours.

Server details

Where does [RD] TEST SERVER sit?

No region comes from [RD] TEST SERVER. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 208.103.169.136:28010.

What Rust version is [RD] TEST SERVER on?

Rust network protocol 2635 and build 168909 on Linux is the build [RD] TEST SERVER runs. Check: protocol. To join, your game must match; Steam handles the update.

What is the performance reading for [RD] TEST SERVER?

Reading: 30 server fps on average across the last 48 hours. It never dropped below 30. Peak entity count: 49,781. Buildings, deployables and all else included. Reading: 5,254 MB of memory at the highest. What players call lag comes from low fps and an entity count on the rise.

What is the uptime on [RD] TEST SERVER, and is it online?

Reading: online. [RD] TEST SERVER answers right now. Reading: uptime. About 33 hours ago it restarted, on its own count. Reading: 33% uptime over the last 7 full days. It was up 56 of 168 hours. The first sighting on Rust Metrics was 20 September 2026.

Rules and settings

What settings and rules apply on [RD] TEST SERVER?

No gather rate appears in the name: [RD] TEST SERVER. The group cap is 4 players, read as quad. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

What map is [RD] TEST SERVER on?

Custom map, size 5,200, on [RD] TEST SERVER. Download the published file from this page.

How to join

How can you get onto [RD] TEST SERVER?

Press F1 in Rust and enter client.connect 208.103.169.136:28010. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect. https://rustdecay.com/ is where its website sits.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2635,^m,gmrust,cs168909,ts4,^o^z,rustmaps

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players Slots: 0.
ts4
Group limit Teams are capped at 4.
v2635
Protocol Your game must run protocol 2635 to get in.
cs168909
Build The server runs game build 168909.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is set.

Wipe schedule

^m
Monthly Facepunch's force wipe sets the monthly cycle here.

Mods and access

^o
Oxide It runs Oxide, also known as uMod.
^z
Modded Plugins or settings make this a modded server.

Other

rustmaps
Custom tag This tag is non-standard, added by the owner or a plugin.

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.