Rust PopulationField survey · Rust servers
Observing 48,284 players 11,675 servers 3,207 with someone on 128 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 8,845habitat unknownfirst seen 13 Sep 2026

TESTING

Online 51.83.150.41:28015 checked 12m ago

moddedcarbon

Measurements

Players now
0/ 500
0% full
7-day average
0
peak 4
Rank
#8,845
top 40%
Last wipe
10d ago
no schedule published
Next wipe
–
no rhythm it keeps
Obs. 1 · sightings

Players

AveragePeak
00.250.50.75102:0011:0020:0005:0014:0023:00

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

05010015020002:0011:0020: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.

Obs. 3 · standing

Rank

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

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

Obs. 4 · the wipe cycle

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 days
usual gap
between real wipes
50%
on rhythm
of its recent wipes
15
wipe-day peak
players, last three wipes
80%
crowd held
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.

Log · wipes seen

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.

Field questions

Quick answers

from the figures on this page

Population

How does TESTING rank against other Rust servers?

By player hours over the last seven days, TESTING places at #8,845, within the top 40% of ranked servers.

How busy is TESTING?

Of its 500 slots, TESTING is using 0 right now. We counted an average of 0 players in the past week, with 4 at the busiest. Look at the last 48 hours and 09:00 UTC stands out: it averaged 0 players.

Tags

What do the server tags on TESTING mean?

What the game's server browser reads from TESTING is this set of tags: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): You can join up to 500 slots; ts8 (Group limit): 8 per team is the default limit; v2635 (Protocol): To join, your game must match protocol 2635; cs168909 (Build): This server runs game build 168909; ptrak (Networking): The standard network layer, RakNet, is in use; $r? (Region code): The region code is left blank; ^z (Modded): Plugins or settings change the game; it is listed under Modded; ^y (Carbon): Carbon provides the plugin framework here. Player count now, queue length and the making of the world all sit in the tags as well, and the top of this page shows them.

Which Rust Population lists and filters include TESTING?

On Rust Population, TESTING is filed under these lists: Modded Rust servers, counted. Filter the server list by Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks and it will show up.

Wipe schedule

What does wipe day look like on TESTING?

Averaged over recent wipes, 15 players were counted at the busiest point. 0 hours after the latest wipe the crowd peaked. In 80% of recent wipes, half the peak was held until the next wipe. The crowd dropped below half by day 1 when it did not hold.

What is the wipe schedule on TESTING?

Irregular times are when TESTING wipes, which leaves no next wipe to predict. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. 10 days 6 hours ago the current world was made.

Map and rules

Which map does TESTING run?

TESTING uses a map the game generates, procedural, at size 1,000 with seed 612351. Size and seed together fix the map, so you can view it on RustMaps from this page.

What are the rules and settings on TESTING?

Nothing in TESTING's name says how gather works. No limit is set beyond the standard 8 players per group. You get survival here, gather, build and raid, as in the standard game. You can raid and fight other players here. You find it under Modded, since plugins or settings change how it plays. You will find Carbon running as plugins. VAC, Valve's anti-cheat, runs here.

About the server

Which version of Rust does TESTING run?

The setup is Rust network protocol 2635 and build 168909 on Windows for TESTING. The protocol must match for you to join, and Steam updates it for you.

Does TESTING run smoothly?

It ran at 128 server fps on average over the last 48 hours, and never went below 125. Entities peaked at 4,021, including buildings, deployables and everything else. Up to 1,054 MB of memory was used. Lag, as players feel it, is low fps combined with a climbing entity count.

Is TESTING online, and how reliable is it?

You will find TESTING online now. About 2 days 4 hours ago, it restarted, according to its uptime. It was up 76% of the time over the last 7 full days, 127 out of 168 hours. The first sighting by Rust Population was on 13 September 2026.

Where is TESTING located?

Nothing published by TESTING states a region. What Rust Population shows is where a server says it is; where the machine actually stands is not looked up. You will find it at 51.83.150.41:28015.

How to join

How do I join TESTING?

Open the console with F1 in Rust and enter client.connect 51.83.150.41:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

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

Game

gmrust
Game mode The game mode is standard Rust survival.
mp500
Max players You can join up to 500 slots.
ts8
Group limit 8 per team is the default limit.
v2635
Protocol To join, your game must match protocol 2635.
cs168909
Build This server runs game build 168909.
ptrak
Networking The standard network layer, RakNet, is in use.
$r?
Region code The region code is left blank.

Mods and access

^z
Modded Plugins or settings change the game; it is listed under Modded.
^y
Carbon Carbon provides the plugin framework here.

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.