RUST METRICSFlight deck · live data
Data live Servers11,669 Players52,726 Populated3,296 Fresh wipes 3 h85 Scan5 min
‹ All servers95.26.140.51:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.140.51:28015 checked 19d ago

moddedoxide
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,637top 62%
Last wipe19d 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 Oct

Top 62% 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

When does Testing server wipe?

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 in play was created 19 days 13 hours ago.

Lists and filters

How should you read the tags on Testing server?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): Slots: 1; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167231 (Build): The server runs game build 167231; ptrak (Networking): Network layer: RakNet, the standard for the game; $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 from Testing server. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

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. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Player count

Where does Testing server sit in the rankings?

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

What is the population on Testing server?

Reading for Testing server: offline at this moment; last seen 19 days ago.

Operator and location

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. The endpoint you need is 95.26.140.51:28015.

What Rust version is Testing server on?

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

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

Check: connection. Testing server is offline at this moment. Last contact was 19 days ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 9 October 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Testing server?

No gather rate appears in the name: Testing server. The group cap is 8 players, which is the default in the game. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. Check: anti-cheat. VAC, Valve's system, is on.

Join

What do you do to join Testing server?

Press F1 in Rust and enter client.connect 95.26.140.51: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?,v2634,gmrust,cs167231,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players Slots: 1.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167231
Build The server runs game build 167231.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.