RUST METRICSFlight deck · live data
Data live Servers11,612 Players35,778 Populated2,872 Fresh wipes 3 h59 Scan5 min
‹ All servers95.26.143.185:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.143.185:28015 checked 44d 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–score 0
Last wipe48d 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
No rank history yet.
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 timing

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 next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 48 days 4 hours ago.

Lists and filters

How should you read the tags on Testing server?

These are the tags Testing server publishes, and the server browser reads them: gmhardcore (Game mode): Check: ruleset. Hardcore, the harsher option; mp1 (Max players): Slots: 1; ts0 (Group limit): No teams here: the setting is switched off; v2633 (Protocol): Protocol 2633: join only on the same game version; cs163794 (Build): The server runs game build 163794; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does Testing server appear in Rust Metrics lists and filters?

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

Population

What player count does Testing server carry?

Status for Testing server: offline. Last seen 44 days 20 hours ago.

Operator and location

Which location does Testing server run from?

Reading: location. Testing server gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. The endpoint you need is 95.26.143.185:28015.

What Rust version is Testing server on?

Rust network protocol 2633 and build 163794 on Windows is the build Testing server runs. To get in, your game needs the same protocol; Steam applies the update.

Is Testing server up, and how often does it stay up?

Testing server reports offline. The last reading came 44 days 20 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 13 September 2026, recorded by Rust Metrics.

Rules and settings

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

Check: gather rate. The name Testing server does not state one. No group limit is published. Mode check gives hardcore; Facepunch's most punishing mode. 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. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.

How to join

How can you get onto Testing server?

Press F1 in Rust and enter client.connect 95.26.143.185:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmhardcore
Game mode Check: ruleset. Hardcore, the harsher option.
mp1
Max players Slots: 1.
ts0
Group limit No teams here: the setting is switched off.
v2633
Protocol Protocol 2633: join only on the same game version.
cs163794
Build The server runs game build 163794.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.