RUST METRICSFlight deck · live data
Data live Servers11,693 Players37,607 Populated2,934 Fresh wipes 3 h91 Scan5 min
‹ All servers95.26.136.240:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.136.240:28015 checked 41d 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#14,458no region published
Last wipe44d 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

When does Testing server wipe?

The rhythm of Testing server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world in play was created 44 days 10 hours ago.

Tags

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

These are the tags Testing server publishes, and the server browser reads them: gmhardcore (Game mode): A harsher set of rules: hardcore; mp1 (Max players): The server holds 1 slots; ts0 (Group limit): Team play is disabled; v2633 (Protocol): Protocol 2633: join only on the same game version; cs164530 (Build): The server runs game build 164530; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show Testing server?

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.

Player count

What position does Testing server hold among Rust servers?

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

What is the population on Testing server?

Testing server is not responding; status offline, last seen 41 days 11 hours ago.

Operator and location

Which location does Testing server run from?

No region tag on Testing server. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 95.26.136.240:28015.

What Rust version is Testing server on?

Version check: Rust network protocol 2633 and build 164530 on Windows, run by Testing server. 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 41 days 11 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 17 September 2026.

Settings and map

What settings and rules apply on Testing server?

No gather rate appears in the name: Testing server. No group limit is published. hardcore, Facepunch's most punishing mode — that is the game 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. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

What map is Testing server on?

Check: map. Procedural, generated by the game, on Testing server.

Join

How can you get onto Testing server?

Check: join. Open Rust, press F1, then enter client.connect 95.26.136.240:28015. Alternatively, use Launch Rust on this page: Steam opens Rust 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 A harsher set of rules: hardcore.
mp1
Max players The server holds 1 slots.
ts0
Group limit Team play is disabled.
v2633
Protocol Protocol 2633: join only on the same game version.
cs164530
Build The server runs game build 164530.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^o
Oxide Plugin framework in use: Oxide (uMod).
^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.