TST8827=
TESTING
Online 51.83.150.41:28015 checked 9m ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server 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.
Rank
daily · 1 is bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe 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.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 17 Oct, 19:12 UTC9d 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.
-
01MODPlayers 220/500
-
02MODPlayers 120/100
-
03MODPlayers 188/225
-
04MODPlayers 34/200
-
05MODPlayers 193/700
-
06MODPlayers 64/1000
Quick answers
From the figures on this page.
Tags
Which Rust Tracker filters and lists carry TESTING?
On Rust Tracker, TESTING sits in these lists: Modded servers, tracked live. On the server list, these filters bring it up: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
How should you read the tags on TESTING?
The game's server browser reads these tags from TESTING: gmrust (Game mode): Rust survival, standard mode; mp500 (Max players): Capacity: 500 slots; ts8 (Group limit): Teams cap at 8; this is the game default; v2635 (Protocol): Your game must be on protocol 2635 to connect; cs168909 (Build): This server runs game build 168909; ptrak (Networking): Network layer is RakNet, which is standard for the game; $r? (Region code): The region code is unset; ^z (Modded): Plugins or settings alter the game, so it is listed under Modded; ^y (Carbon): Plugin framework: Carbon. At the top of this page you also get the queue, the players now and the world's creation time, all from the tags.
Wipe Times
What should you expect on TESTING when wipe day lands?
The average peak across recent wipes: 15 players. The peak on the latest wipe came 0 hours after it. The crowd stayed above half the peak until the next wipe in 80% of recent wipes. In the other cases, half the peak was lost by day 1.
When does TESTING wipe?
Irregular wipe times at TESTING: there is no next wipe to predict. Thursday 5 November at 19:00 UTC is the next monthly force wipe. No server is exempt. Its world went live 9 days 23 hours.
Server Details
How reliable is TESTING, and is it online now?
TESTING is up and online at this moment. The uptime it reports puts the last restart about 46 hours ago. 103 of 168 hours up over the last 7 full days: 61% uptime. The first sighting by Rust Tracker was 13 September 2026.
Which Rust version is confirmed on TESTING?
Rust network protocol 2635 and build 168909 on Windows is what TESTING runs. To join, your game must be on the same protocol; Steam handles the update.
What is performance like on TESTING?
Server fps held an average of 128 across the last 48 hours, never below 126. Buildings, deployables and the rest of the world took it to a maximum of 4,038 entities. It drew as much as 1,015 MB of memory. A climbing entity count and low fps are what register as lag for players.
What location is TESTING hosted in?
No region is published by TESTING. Rust Tracker displays the location a server claims; it does not verify where the machine sits. You connect at 51.83.150.41:28015.
Population
What is the player count on TESTING?
Tracking TESTING: 0 of 500 slots filled. Over seven days: average 0, peak 4 players. At 20:00 UTC it drew its highest average of the last 48 hours: 3 players.
What rank does TESTING carry among Rust servers?
Seven-day player hours put TESTING at #8,827, within the top 40% of all ranked servers.
Settings
Which settings and rules are confirmed on TESTING?
Nothing in TESTING's name states a gather rate. Up to 8 players per group, the game's default. survival is the game mode, gather, build and raid: the standard game. Raiding and PvP are permitted between players. The server browser lists it under Modded, where plugins or settings change the game. Plugins on it: Carbon. VAC is on, Valve's anti-cheat.
Which map is loaded on TESTING?
A procedural map of size 1,000 runs on TESTING, generated by the game from seed 612351. Look at it on RustMaps from this page: equal size and seed return the same map.
How to Join
How do you get onto TESTING?
To connect: start Rust, press F1, enter client.connect 51.83.150.41:28015 in the console. Or use Launch Rust on this page to open Rust through Steam and join.
Server tags
What each one means.
Published 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.