RUST METRICSFlight deck · live data
Data live Servers11,658 Players32,604 Populated2,794 Fresh wipes 3 h75 Scan5 min
‹ All servers95.26.137.200:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.137.200:28015 checked 43d 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,288no 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 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 timing

What wipe timing does Testing server follow?

The rhythm of Testing server'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. 44 days 12 hours ago the current world was made.

Lists and filters

How should you read the tags on Testing server?

Check: tags. The game's server browser reads gmhardcore (Game mode): Hardcore ruleset, the harsher one; mp1 (Max players): The server holds 1 slots; ts0 (Group limit): No teams here: the setting is switched off; v2633 (Protocol): Your game must run protocol 2633 to get in; cs163794 (Build): The server runs game build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): Plugin framework in use: Oxide (uMod); ^z (Modded): Modded: plugins or settings depart from the stock game from Testing server. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Testing server?

Rust Metrics lists featuring Testing server: 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,288 on seven-day player hours, top – of all ranked servers.

How full does Testing server get?

Reading for Testing server: offline at this moment; last seen 43 days 15 hours ago.

Server details

Where does Testing server sit?

Reading: location. Testing server gives no region. Note: Rust Metrics shows the location a server gives, not where the machine stands. Connect using 95.26.137.200:28015.

What Rust version is Testing server on?

Rust network protocol 2633 and build 163794 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?

Testing server reports offline. The last reading came 43 days 15 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 15 September 2026.

Map and rules

What settings and rules apply on Testing server?

Check: gather rate. The name Testing server does not state one. The group limit is not published. hardcore, Facepunch's most punishing mode — that is the game mode. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is Testing server on?

Procedural map on Testing server, made by the game's generator.

How to join

How can you get onto Testing server?

To join: start Rust, press F1 and type client.connect 95.26.137.200: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,cs163794,ts0,^o^z

Game

gmhardcore
Game mode Hardcore ruleset, the harsher one.
mp1
Max players The server holds 1 slots.
ts0
Group limit No teams here: the setting is switched off.
v2633
Protocol Your game must run protocol 2633 to get in.
cs163794
Build The server runs game build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

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