Online 51.83.150.41:28015 checked 13m ago
TESTING
By the numbersMatch stats
against its 500 slotsThe story of the match
Players, performance and rank, hour by hour and day by day.
CrowdPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
FitnessServer performance
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.
FormRank
daily · 1 is bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
FixturesWipe schedule
no rhythm it keepsIts wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
ResultsWipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Quick answers
From the figures on this page.
About the server
Is TESTING online, and how reliable is it?
Online now, TESTING is up. About 2 days 12 hours ago is when it restarted, judging by its reported uptime. 76% of the time over the last 7 full days, which is 127 of 168 hours up. On 13 September 2026, Rust Player Stats saw it for the first time.
Does TESTING run smoothly?
128 server fps on average over 48 hours, and never under 125. Its entity count reached 4,021: buildings, deployables and the rest of the world. The memory ceiling was 1,061 MB. A climbing entity count plus low fps: that is lag, as players experience it.
Which Rust version is TESTING on?
On Windows, TESTING runs Rust network protocol 2635 and build 168909. To get in, your game needs the same protocol; Steam handles the update.
Where is TESTING located?
There is no region published on TESTING. Rust Player Stats takes the server's word on where it is and does not look up the machine's real location. You will find it at 51.83.150.41:28015.
Server tags
What do the server tags on TESTING mean?
The game's server browser reads these tags from TESTING: gmrust (Game mode): Survival, standard Rust style; mp500 (Max players): It holds 500 slots; ts8 (Group limit): The default 8 per team applies here; v2635 (Protocol): Your game must be on protocol 2635 to get in; cs168909 (Build): The game build here is 168909; ptrak (Networking): The network layer is RakNet, the standard one; $r? (Region code): The region code is left blank; ^z (Modded): Modded is its category: plugins or settings change how it plays; ^y (Carbon): It uses Carbon for plugins. The tags carry more besides: present players, queue length and when the world was made, all displayed at the top of this page.
Which Rust Player Stats lists and filters include TESTING?
The Rust Player Stats lists that include TESTING are: Modded Rust servers, live. These filters on the server list bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Map and rules
Which map is running on TESTING?
The procedural map on TESTING is size 1,000, generated by the game from seed 612351. Same size, same seed, same map, so RustMaps shows it from this page.
What are the rules and settings on TESTING?
No gather rate appears in the name of TESTING. The cap is 8 players per group, the game's default. survival, build, gather and raid in the standard game. Fighting and raiding between players is allowed. The server browser files it under Modded: plugins or settings change the game. It runs plugins: Carbon. VAC is on, so Valve's anti-cheat is watching.
Live counts
How full is TESTING right now?
2 of 500 slots are filled on TESTING right now. Averaged across seven days: 0 players. The high point: 4.
Where does TESTING sit in the rankings?
Player hours over seven days place TESTING at #8,840, among the top 40% of ranked servers.
Wipe schedule
What is the wipe schedule on TESTING?
No next wipe can be predicted for TESTING, because it wipes at irregular times. The monthly force wipe hits every Rust server, and the next one is on Thursday 5 November at 19:00 UTC. The world it runs now was made 10 days 14 hours ago.
What does wipe day look like on TESTING?
At their busiest, its recent wipes drew 15 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 80% of recent wipes. It fell below half by day 1 when it didn't hold.
Joining the server
How do I join TESTING?
Press F1 in Rust, bring up the console and enter client.connect 51.83.150.41:28015. The Launch Rust button here does the same, opening Rust via Steam and connecting you.
GlossaryServer tags
what each one meansPublished as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^z,^y
Game
gmrust
mp500
ts8
v2635
cs168909
ptrak
$r?
Mods and access
^z
^y
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.