RUST METRICSFlight deck · live data
Data live Servers11,685 Players49,486 Populated3,263 Fresh wipes 3 h130 Scan5 min
‹ All servers95.26.140.86:28015
Offline Full Queue Fresh wipe Wipe due No query

Testing server

Offline 95.26.140.86:28015 checked 30d ago

moddedoxide
COM 1 · connect
Launch Rust and join

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,490top 61%
Last wipe34d 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
15k10k15k20k27 Sep28 Sep30 Sep1 Oct3 Oct4 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 timing

How often does Testing server wipe, and when?

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 it runs now was made 34 days 8 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: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set; ^o (Oxide): It runs Oxide, also known as uMod; ^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. Reading: server list filters. It comes up under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.

Occupancy

What position does Testing server hold among Rust servers?

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

How full does Testing server get?

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

Server

What location is Testing server hosted in?

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.140.86:28015.

What Rust version is Testing server on?

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

Reading: offline. Testing server last answered 30 days 19 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 27 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 limit is set beyond the default. Groups take up to 8 players. Mode check gives survival; the normal game: build, gather, raid. Players can raid each other and fight. That is permitted here. Plugins or settings change the game, so it is listed as Modded. Plugin count: Oxide. Anti-cheat reading: VAC on, Valve's system.

Connection

What do you do to join Testing server?

To join: start Rust, press F1 and type client.connect 95.26.140.86: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,gmrust,cs165217,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code Region code: none set.

Mods and access

^o
Oxide It runs Oxide, also known as 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.