At press time 11,706 servers60,014 players142 fresh wipes Revised every five minutes
Rust Server StatsThe record of every Rust server, kept current.

An entry in the registerNo. 6,535

TESTING

Online 51.83.150.41:28015 checked 30m ago

TESTING is a Rust server. At the last count it had 0 players of a possible 500; over the past week it averaged 0, with a peak of 7. It stands at No. 6,535 of the ranked servers, the top 29%. It last wiped 12d ago. Its own tags class it as modded, carbon.

§ 1Attendance

AveragePeak
0246802:0011:0021:0005:0014:0023:00

Hourly average and peak, UTC.

§ 2Performance

05010015020002:0011:0021:0005:0014:0023: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.

§ 3Standingthe rank, daily · 1 is best

RankRank in region
15k10k15k20k20 Sep28 Sep6 Oct13 Oct21 Oct29 Oct

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

§ 4The wipe scheduleno rhythm it keeps

Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.

The rhythm
Usual gap3 days

between real wipes

On rhythm50%

of its recent wipes

Wipe-day peak15

players, last three wipes

Crowd held80%

else halves by day 1

The first 48 hours of its last wipes

Sat 17 OctThu 15 OctMon 12 Oct
010203040+0h+9h+19h+28h+38h+47h

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

§ 5The record of wipesnewest first

WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 19:12 UTC12d ago 1 – running 0
Thu 15 Oct, 14:58 UTC14d ago 18 held half 2.2 days 3
Mon 12 Oct, 14:59 UTC17d ago 25 held half 3 days 0
Thu 8 Oct, 14:58 UTC21d ago 12 held half 4 days 4
Mon 5 Oct, 15:00 UTC24d ago 24 held half 3 days 2
Thu 1 Oct, 17:57 UTC FW28d ago 23 halved by day 1 3.9 days 1
Mon 28 Sep, 15:58 UTC31d ago 24 held half 3.1 days 2
Fri 25 Sep, 17:03 UTC34d ago 22 held half 3 days 2
Mon 21 Sep, 15:57 UTC38d ago 6 halved by day 1 4 days 0
Mon 14 Sep, 15:56 UTC45d ago 25 halved by day 2 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.

§ 6Similar serversthe same kind of game, then region, group limit, rate and wipes

  1. 1 ShockRust | Blue | NoLimit21/500 no group limit · 149 on average
  2. 2 МИНИ-КАРТА 2Х | STORM | FPS+ 28.10132/100 EU · groups of 8+ · weekly · 128 on average
  3. 3 RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.1036/225 EU · groups of 16+ · weekly · 121 on average
  4. 4 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.1010/700 EU · groups of 16+ · monthly · 96 on average
  5. 5 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.1044/700 EU · groups of 16+ · monthly · 93 on average
  6. 6 RustSpain.com | EU Main182/215 EU · groups of 12+ · weekly · 85 on average

§ 7Questions answeredfrom the figures in this entry

Server details

What Rust version is TESTING on?

The server TESTING is on Rust network protocol 2635 and build 168909, hosted on Windows. To join, your game must be on the same protocol; Steam handles the update.

How reliable is TESTING, and is it online now?

The records show TESTING online at the time of this check. Of note: the reported uptime places the last restart about 12 hours ago. The records show 85% uptime over the last 7 full days: 143 of 168 hours up. Its earliest entry at Rust Server Stats is dated 13 September 2026.

Does TESTING hold a steady frame?

The records show an average of 127 server fps over 48 hours, never below 109. Of note: 4,815 entities at the peak, counting buildings, deployables and the rest. The memory peak was 1,216 MB. An entity count climbing and fps running low are felt in-game as lag.

In which location does TESTING sit?

The server publishes no region: TESTING. The location Rust Server Stats shows is the one a server states; the machine's own location is not looked up. 51.83.150.41:28015 — that is the address.

The rules and map

What map does TESTING put players on?

TESTING runs a procedural map, generated by the game, of size 1,000 with seed 612351. Because size and seed fix the map, it can be viewed on RustMaps from here.

The rules and settings of TESTING: what are they?

No gather rate appears in the name of TESTING. The group limit is 8 players, the game's default. Play is survival, gather, build and raid: the standard game. Player-versus-player fighting and raiding are enabled. Plugins or settings change the game; it appears under Modded in the browser. Carbon plugins are in use. The VAC anti-cheat from Valve is active.

The players

What are the player numbers on TESTING?

At the latest count TESTING has 0 players, with 500 slots in total. Over seven days the mean is 0 players, with a peak of 7. Of the last 48 hours, 19:00 UTC drew the highest average: 7 players.

What position does TESTING hold among Rust servers?

The seven-day player-hour table places TESTING at #6,535, within the top 29% of ranked servers.

The tags and lists

TESTING sits in which Rust Server Stats lists and filters?

These are the Rust Server Stats lists that include TESTING: Modded Rust servers. On the server list it comes up under these filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

How should the tags on TESTING be read?

gmrust (Game mode): Standard survival, as Rust plays it; mp500 (Max players): Slot count: 500; ts8 (Group limit): 8 to a team, which is the default; v2635 (Protocol): The game version must match protocol 2635 to join; cs168909 (Build): Build 168909; ptrak (Networking): Standard network layer: RakNet; $r? (Region code): The region code is not set; ^z (Modded): Modded: settings or plugins have changed the game; ^y (Carbon): Plugin framework: Carbon — that is the set of tags TESTING publishes for the game's browser. The tags include current players, queue and the time the world was made; the top of this page shows them.

The wipes

What is the shape of wipe day on TESTING?

Averaged over recent wipes, the crowd reached 15 at its busiest. 0 hours into the latest wipe the crowd reached its peak. Above half that peak until the next wipe: the crowd held in 80% of recent wipes. The fall below half came by day 1 where the crowd did not hold.

The wipe timetable for TESTING: what does it show?

There is no next wipe to predict: TESTING wipes irregularly. On Thursday 5 November at 19:00 UTC the monthly force wipe takes every Rust server, without exception. The world now in play was generated 12 days 5 hours ago.

Joining the server

Which steps join TESTING?

Join on this page with Launch Rust, which opens Rust through Steam and connects you, or open the console with F1 and enter client.connect 51.83.150.41:28015.

§ 8Key to the tagswhat each one means

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

Game

gmrust
Game mode Standard survival, as Rust plays it.
mp500
Max players Slot count: 500.
ts8
Group limit 8 to a team, which is the default.
v2635
Protocol The game version must match protocol 2635 to join.
cs168909
Build Build 168909.
ptrak
Networking Standard network layer: RakNet.
$r?
Region code The region code is not set.

Mods and access

^z
Modded Modded: settings or plugins have changed the game.
^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.