RUST METRICSFlight deck · live data
Data live Servers11,865 Players95,534 Populated3,881 Fresh wipes 3 h381 Scan5 min
‹ All servers188.236.104.213:28015
Offline Full Queue Fresh wipe Wipe due No query

testserver

Offline 188.236.104.213:28015 checked 17d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 1 /10

Players now

10% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#13,384top 61%
Last wipe22d agono schedule published
Next wipe–no wipe seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k11 Oct13 Oct14 Oct16 Oct17 Oct19 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does testserver follow?

The rhythm of testserver'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. The world it runs now was made 22 days 1 hours ago.

Tags

Which tags does testserver carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts5 (Group limit): You may team up with at most 5; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167058 (Build): The server runs game build 167058; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server from testserver. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does testserver appear in Rust Metrics lists and filters?

Rust Metrics lists featuring testserver: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Population

Where does testserver sit in the rankings?

Player hours over seven days put testserver at #13,384, in the top 61% of all ranked servers.

How full does testserver get?

Reading for testserver: offline at this moment; last seen 17 days 3 hours ago.

Server details

Where does testserver sit?

No region comes from testserver. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 188.236.104.213:28015.

What Rust version is testserver on?

Reading: testserver, Rust network protocol 2634 and build 167058, Windows. Check: protocol. To join, your game must match; Steam handles the update.

Is testserver up, and how often does it stay up?

Check: connection. testserver is offline at this moment. Last contact was 17 days 3 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 10 October 2026.

Map and rules

How is testserver configured, and what rules are in force?

No gather rate appears in the name: testserver. Group size, maximum: 5 players. The mode is survival. Note the following: the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Which map is live on testserver?

The game generates a procedural map for testserver.

How to join

How do you connect to testserver?

Check: join. Open Rust, press F1, then enter client.connect 188.236.104.213:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp10,ptrak,$r?,v2634,gmrust,cs167058,ts5,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts5
Group limit You may team up with at most 5.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167058
Build The server runs game build 167058.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.