StatusLive Servers online11,662 Players43,563 Populated3,033 Wiped · 3 h101 Interval5 min Date28 OCT 2026

DWG RG-S11811Server sheetchecked 8m ago

TESTSERVER

Online 141.95.13.69:26111 checked 8m ago

moddedcarbon
Connect
Players now 0/ 50 0% full
7-day average0peak 1
Rank#11,811top 53%
Last wipe19d agono schedule published
Next wipe–too few wipes seen yet
Fig. 1

Players

AveragePeak
00.250.50.75102:0011:0020:0006:0015:0000:00

Hourly average and peak, UTC.

Fig. 1Players on TESTSERVER
Fig. 2

Server performance

05010015020002:0011:0020:0006:0015:0000:00

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, measured since 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

Fig. 2FPS, entities and memory
Fig. 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Sep28 Sep5 Oct13 Oct20 Oct28 Oct

Top 53% of all ranked servers. Ranked on player hours over the last seven days.

Fig. 3Rank on player hours, daily
Schedule

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

usual gap7 daysbetween real wipes
wipe-day peak0players, last three wipes

The first 48 hours of its last wipes

Thu 8 OctThu 1 Oct
01234+0h+9h+19h+28h+38h+47h
Fig. 4Players each hour from the hour of the wipe

Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.

ScheduleExpected wipes
Log

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 18:07 UTC19d ago 0 – running 0
Thu 1 Oct, 18:07 UTC FW26d ago 0 – 7 days 0

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.

Table 1Wipe log
Similar assemblies

Similar servers

the same kind of game, then region, group limit, rate and wipes
01
ShockRust | Blue | NoLimitno group limit · 161 on average
27 / 500
02
МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average
134 / 100
03
RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 114 on average
41 / 225
04
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 87 on average
33 / 700
05
RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average
9 / 200
06
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 83 on average
11 / 1000
Ref.Similar
General notes

Quick answers

from the figures on this page

Server data

How reliable is TESTSERVER, and is it online now?

Right now, TESTSERVER is recorded as online. About 38 hours ago is when it last restarted, measured from the uptime it reports. 168 of 168 hours up over the last 7 full days, which is 100% of the time. First seen by Rust Graphs on 13 September 2026.

Is TESTSERVER stable in the figures recorded?

Average server fps over the last 48 hours is 98; the lowest was 57. Counted at its highest: 122,652 entities, buildings, deployables and the rest of the world included. Memory use peaked at 6,225 MB. What players feel as lag is low fps together with a climbing entity count.

What location is recorded for TESTSERVER?

There is no region published by TESTSERVER. No lookup of the machine's location is done: Rust Graphs shows where a server says it is. It is reached at 141.95.13.69:26111.

On which Rust version is TESTSERVER running?

On Linux, TESTSERVER runs Rust network protocol 2635 and build 168909. To join, your game must be on the same protocol; Steam handles the update.

Counts

How many players are plotted on TESTSERVER?

At the last refresh, TESTSERVER recorded 0 players across 50 slots. Averaged across seven days, the player count is 0, with a peak of 1. Averaged over the last 48 hours, the player count is highest at 04:00 UTC: 1 players.

In the rankings, which position does TESTSERVER hold?

Within the top 53% of all ranked servers: TESTSERVER at #11,811 for player hours, seven days recorded.

Schedules

What happens on TESTSERVER on the day of a wipe?

An average of 0 players was recorded at the busiest point of its recent wipes. 0 hours after the latest wipe, the crowd peaked.

Which times and days are wipes plotted at on TESTSERVER?

The record of TESTSERVER's wipes is too short to tell its rhythm. Thursday 5 November at 19:00 UTC is the date of the next monthly force wipe, when all Rust servers wipe. 19 days 7 hours ago the current world was made.

Rules and settings

What settings and rules apply on TESTSERVER?

The name of TESTSERVER records no gather rate. Eight players per group: the default for the game. It runs the survival game mode, the standard game: gather, build, raid. Raiding and player combat are permitted. Listed as Modded in the server browser: the game is changed by plugins or settings. The plugin count is Carbon. Anti-cheat: VAC, from Valve, is on.

Which map has TESTSERVER loaded?

TESTSERVER runs a procedural map of size 4,500 with seed 246426222, generated by the game. Size and seed fix the map, so this page links it on RustMaps for viewing.

Lists and filters

On Rust Graphs, which lists and filters contain TESTSERVER?

These Rust Graphs lists include TESTSERVER: Modded Rust servers. These filters on the server list return it: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Which meaning is attached to each tag on TESTSERVER?

gmrust (Game mode): Standard survival, as Rust plays; mp50 (Max players): Slots: 50; ts8 (Group limit): Teams are capped at 8, the default setting; v2635 (Protocol): To join, your game must be on protocol 2635; cs168909 (Build): 168909 is the game build; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings; the listing is Modded; ^y (Carbon): Plugin framework: Carbon are the tags TESTSERVER publishes; the game's server browser reads them. Current players, queue length and world creation time are in the tags as well, and appear at the top of this page.

How to join

By what method do you join TESTSERVER?

Enter client.connect 141.95.13.69:26111 in the console, opened with F1 in Rust. Launch Rust on this page is the other way: it opens Rust through Steam and connects you.

NotesAnswered from the figures
Key

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y

Game

gmrust
Game mode Standard survival, as Rust plays.
mp50
Max players Slots: 50.
ts8
Group limit Teams are capped at 8, the default setting.
v2635
Protocol To join, your game must be on protocol 2635.
cs168909
Build 168909 is the game build.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code field is empty.

Mods and access

^z
Modded The game is changed by plugins or settings; the listing is Modded.
^y
Carbon Plugin framework: Carbon.

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.

KeyTag string decoded