Rust Dashboard53,688 playing

TESTING

Online 51.83.150.41:28015 checked 10m ago

moddedcarbon

Players now

Live
0of 500
Full
0%
In queue
0
Peak, 48 hours
2
Peak, 7 days
4

0% full

Mon 10:00Wed 08:00players each hour · 48 hours · UTC

Rank

#8,728

top 39%

7-day average

0

peak 4

Last wipe

10d ago

no schedule published

Next wipe

–

no rhythm it keeps

Players

AveragePeak
00.511.5210:0019:0004:0014:0023:0008:00

Hourly average and peak, UTC.

Server performance

05010015020010:0019:0004:0014:0023:0008: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.

Rank

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

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

Wipe schedule

no rhythm it keeps

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

3 daysusual gapbetween real wipes
50%on rhythmof its recent wipes
15wipe-day peakplayers, last three wipes
80%crowd heldelse 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.

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sat 17 Oct, 19:12 UTC10d ago 1 – running 0
Thu 15 Oct, 14:58 UTC12d ago 18 held half 2.2 days 3
Mon 12 Oct, 14:59 UTC15d ago 25 held half 3 days 0
Thu 8 Oct, 14:58 UTC19d ago 12 held half 4 days 4
Mon 5 Oct, 15:00 UTC22d ago 24 held half 3 days 2
Thu 1 Oct, 17:57 UTC FW26d ago 23 halved by day 1 3.9 days 1
Mon 28 Sep, 15:58 UTC29d ago 24 held half 3.1 days 2
Fri 25 Sep, 17:03 UTC32d ago 22 held half 3 days 2
Mon 21 Sep, 15:57 UTC36d ago 6 halved by day 1 4 days 0
Mon 14 Sep, 15:56 UTC43d 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.

Similar servers

the same kind of game, then region, group limit, rate and wipes
  1. 1
    ShockRust | Blue | NoLimitno group limit · 155 on average
    157/ 500
  2. 2
    МИНИ-КАРТА 2Х | STORM | FPS+ 24.10EU · groups of 8+ · weekly · 128 on average
    130/ 100
  3. 3
    RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10EU · groups of 16+ · weekly · 115 on average
    184/ 225
  4. 4
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10EU · groups of 16+ · monthly · 88 on average
    111/ 700
  5. 5
    RustSpain.com | EU MainEU · groups of 12+ · weekly · 87 on average
    8/ 200
  6. 6
    404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10EU · groups of 16+ · monthly · 84 on average
    45/ 1000

Quick answers

from the figures on this page

Server details

Is TESTING online, and how reliable is it?

TESTING is up and taking players now. The uptime it reports puts its last restart about 2 days 13 hours ago. It was online 76% of the last 7 full days, which is 127 of 168 hours. Rust Dashboard logged it for the first time on 13 September 2026.

Which version of Rust does TESTING run?

TESTING runs Rust network protocol 2635 and build 168909, and Windows is the system under it. Joining needs the same protocol on your side, and Steam handles that update.

Where is TESTING located?

There is no region on TESTING. Rust Dashboard takes the location a server gives; the machine's real position is not checked. 51.83.150.41:28015 is where it lives.

Does TESTING run smoothly?

The last 48 hours gave an average of 128 server fps, and it never went under 125. The world held as many as 4,021 entities, counting buildings, deployables and all the rest. It drew as much as 1,061 MB of memory at peak. When fps is low and entities keep piling up, players notice it as lag.

Tags, lists

Which Rust Dashboard lists and filters include TESTING?

These Rust Dashboard lists include TESTING: Modded Rust servers, live now. It appears under these filters when you browse the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.

What do the server tags on TESTING mean?

These are the tags TESTING publishes, read by the game's server browser: gmrust (Game mode): Standard Rust survival is the game mode; mp500 (Max players): 500 is the slot count; ts8 (Group limit): Teams are capped at 8, the default the game ships with; v2635 (Protocol): The game protocol is 2635; your build has to match it to join; cs168909 (Build): The game build is 168909; ptrak (Networking): RakNet is the standard network layer for the game, and it is what runs here; $r? (Region code): This server sets no region code; ^z (Modded): Plugins or settings alter the game, so it appears under Modded; ^y (Carbon): This one runs Carbon for plugins. At the top of this page you'll find the current players, the queue and the world's creation time, which the tags carry too.

Player counts

How busy is TESTING?

TESTING has 0 of its 500 slots filled at the moment. Its seven-day average is 0 players, and it reached 4 at the highest. Across the last 48 hours, the peak came at 08:00 UTC with an average of 0 players.

How does TESTING rank against other Rust servers?

Ranked #8,728 on the last seven days of player hours, TESTING is in the top 39% of all ranked servers.

Wipe schedule

What does wipe day look like on TESTING?

The average busiest point of its recent wipes was 15 players. Peak crowd on the latest wipe came 0 hours after it began. Above half that peak until the next wipe: that held in 80% of recent wipes. By day 1 it had fallen below half, where the crowd did not hold.

What is the wipe schedule on TESTING?

There is no next wipe to predict: TESTING wipes at irregular times. The monthly force wipe applies to every Rust server, and the next one falls on Thursday 5 November at 19:00 UTC. The world it runs now dates from 10 days 14 hours ago.

Settings

What are the rules and settings on TESTING?

The name of TESTING gives no gather rate. Groups hold up to 8 players, the default for the game. survival is the mode here, the usual game, where you gather, build and raid. You can fight other players and raid their bases. Modded is its category in the browser, because plugins or settings change the game. The plugin count is Carbon. VAC is on: that is Valve's anti-cheat.

Which map does TESTING run?

A procedural map of size 1,000 with seed 612351 is what TESTING runs, generated by the game. This page links to RustMaps, where the map looks the same for its size and seed.

Connect

How do I join TESTING?

The console in Rust opens with F1, and client.connect 51.83.150.41:28015 goes in there. Launch Rust on this page is the other route, opening Rust through Steam to connect you.

Server tags

what each one means

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

Game

gmrust
Game mode Standard Rust survival is the game mode.
mp500
Max players 500 is the slot count.
ts8
Group limit Teams are capped at 8, the default the game ships with.
v2635
Protocol The game protocol is 2635; your build has to match it to join.
cs168909
Build The game build is 168909.
ptrak
Networking RakNet is the standard network layer for the game, and it is what runs here.
$r?
Region code This server sets no region code.

Mods and access

^z
Modded Plugins or settings alter the game, so it appears under Modded.
^y
Carbon This one runs Carbon for plugins.

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.