RUST METRICSFlight deck · live data
Data live Servers11,683 Players54,666 Populated3,397 Fresh wipes 3 h92 Scan5 min
‹ All servers95.26.139.0:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.139.0:28015 checked 22d 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,778top 61%
Last wipe22d 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
15k10k15k20k6 Oct7 Oct9 Oct10 Oct12 Oct13 Oct

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

How often does Testing server wipe, and when?

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

Tags

How should you read the tags on Testing server?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; 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; cs166652 (Build): Game build reading: 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Check: category. Modded, because plugins or settings alter the game from Testing 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. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

Where does Testing server sit in the rankings?

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

What player count does Testing server carry?

Reading for Testing server: offline at this moment; last seen 22 days 7 hours 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.139.0:28015.

What Rust version is Testing server on?

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

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

Check: connection. Testing server is offline at this moment. Last contact was 22 days 7 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 5 October 2026.

Rules and settings

What settings and rules apply on Testing server?

No gather rate appears in the name: Testing server. 8 players per group, the default value. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. Listing: Modded. Plugins or settings change the game. Plugin count: Oxide. VAC is on. That is Valve's anti-cheat.

How to join

What do you do to join Testing server?

Check: join. Open Rust, press F1, then enter client.connect 95.26.139.0: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?,v2634,gmrust,cs166652,ts8,^o^z

Game

gmrust
Game mode Survival, as standard Rust plays it.
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.
cs166652
Build Game build reading: 166652.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code The region field is empty.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Check: category. Modded, because plugins or settings alter the 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.