RUST METRICSFlight deck · live data
Data live Servers11,842 Players88,461 Populated4,024 Fresh wipes 3 h178 Scan5 min
‹ All servers95.26.136.215:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.136.215:28015 checked 40d ago

teams off moddedoxidehardcore
COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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,998no region published
Last wipe40d 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
15k10k15k20k20 Sep21 Sep22 Sep23 Sep24 Sep
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 Testing server follow?

Its rhythm cannot be told from the wipes of Testing server on record: there are too few. 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 40 days 22 hours ago.

Lists and filters

Which tags does Testing server carry, and what do they mean?

Check: tags. The game's server browser reads gmhardcore (Game mode): Check: ruleset. Hardcore, the harsher option; mp1 (Max players): 1 slots in total; ts0 (Group limit): No teams here: the setting is switched off; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): Game build reading: 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game from Testing server. 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 Testing server?

On Rust Metrics, Testing server sits in these lists: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Game mode: Hardcore; Server tag: Modded ^z and Oxide ^o.

Population

What position does Testing server hold among Rust servers?

Ranking for Testing server: #13,998 on seven-day player hours, top – of all ranked servers.

What is the population on Testing server?

Status for Testing server: offline. Last seen 40 days 22 hours ago.

Server

Where does Testing server sit?

No region tag on Testing server. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 95.26.136.215:28015.

What Rust version is Testing server on?

Rust network protocol 2633 and build 164530 on Windows is the build Testing server runs. Matching protocol is required to join. Let Steam update your game.

What is the uptime on Testing server, and is it online?

Check: connection. Testing server is offline at this moment. Last contact was 40 days 22 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 17 September 2026.

Rules and settings

How is Testing server configured, and what rules are in force?

Reading the name gives no gather rate for Testing server. The group limit is not published. Mode check gives hardcore; Facepunch's most punishing mode. Combat and raiding against other players are on. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

Connection

How do you connect to Testing server?

To join: start Rust, press F1 and type client.connect 95.26.136.215:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2633,gmhardcore,cs164530,ts0,^o^z

Game

gmhardcore
Game mode Check: ruleset. Hardcore, the harsher option.
mp1
Max players 1 slots in total.
ts0
Group limit No teams here: the setting is switched off.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build Game build reading: 164530.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Modded: plugins or settings depart from the stock game.

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.