TESTING
Online 51.83.150.41:28015 checked 8m ago
Stats
- Players
- 0/ 500
- 0% full
- Slots
- 500open
- 500 max players
- 7-day avg
- 0
- 7-day average · peak 4
- FPS
- 127
- server frames a second, the latest hour; the bar fills at 60
- Uptime
- 2d 2h
- since its last restart; the bar fills at a day
- Rank
- #8,833
- top 40%
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 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 wipesQuick answers
from the figures on this pageHow it plays
Which map is loaded on TESTING?
TESTING runs a procedural map of size 1,000 with seed 612351, generated by the game. Look at it on RustMaps from this page: identical size and seed give an identical map.
What are the rules and settings on TESTING?
The name of TESTING carries no gather rate. 8 players is the group cap, unchanged from the game's default. It plays as survival, the usual game, with gathering, building and raiding. Raids and player combat are part of the game. The server browser lists it as Modded: plugins or settings alter the game. Plugins in play: Carbon. VAC, Valve's anti-cheat, is switched on.
Reset times
What is the wipe schedule on TESTING?
TESTING wipes whenever it likes, so no next wipe can be predicted. Every Rust server takes the force wipe each month; Thursday 5 November at 19:00 UTC is the date of the next. The world it runs now dates from 10 days 3 hours.
What happens on TESTING when wipe day arrives?
The average peak across its recent wipes is 15 players. On the latest wipe, 0 hours in, the crowd hit its peak. 80% of its recent wipes held more than half the peak all the way to the next wipe. The wipes that did not hold saw the count dip below half by day 1.
Lists and filters
What do the server tags on TESTING mean?
The server browser reads these tags from TESTING: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): It holds 500 slots; ts8 (Group limit): Team size is capped at 8, which is the game default; v2635 (Protocol): Join only if your game is on protocol 2635; cs168909 (Build): Build: 168909; ptrak (Networking): The network layer is RakNet, Rust's standard one; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make changes, so it sits under Modded; ^y (Carbon): Carbon is the plugin framework in use. Player count now, queue length and world creation time sit at the top of this page, taken from the tags.
Which Rust Leaderboard lists and filters include TESTING?
These Rust Leaderboard lists count TESTING among them: Best modded Rust servers. Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks are the filters that surface it on the server list.
Server facts
Which Rust version is TESTING running?
The build behind TESTING: Rust network protocol 2635 and build 168909 on Windows. The protocol has to match on both sides for a join; Steam keeps yours updated.
Is TESTING online right now, and how steady has it been?
TESTING is up, live and reachable this moment. About 2 days 2 hours ago is when it last restarted, judged by the uptime it reports. Of the 168 hours in the last 7 full days it was up for 103, or 61%. Rust Leaderboard logged it for the first time on 13 September 2026.
How well does TESTING perform?
128 server fps on average across the last 48 hours, never dropping below 125. Up to 4,021 entities were in play, buildings and deployables among them. The top memory figure was 1,054 MB. Players feel lag when fps drops and the entity count keeps climbing.
Where in the world is TESTING hosted?
Nothing about a region is published by TESTING. Rust Leaderboard shows the location a server claims and does not look up the machine's real position. 51.83.150.41:28015 is its address.
The crowd
Where does TESTING sit on the leaderboard?
Player hours over seven days put TESTING at #8,833, among the top 40% of ranked servers.
How many players are on TESTING right now?
On TESTING, 0 players are in and 500 slots are on the board. Its average over the past week is 0 players, peaking at 4. The busiest point in the last 48 hours was 09:00 UTC, averaging 0 players.
How to join
How do I join TESTING?
In the Rust console (F1) enter client.connect 51.83.150.41:28015. Launch Rust from this page instead and it opens the game through Steam and joins for you.