TESTING
Online 51.83.150.41:28015 checked 13m ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 wipes| Server | Profile | Players now |
|---|---|---|
| ShockRust | Blue | NoLimit | no group limit · 162 on average | 35 / 500 |
| МИНИ-КАРТА 2Х | STORM | FPS+ 24.10 | EU · groups of 8+ · weekly · 128 on average | 129 / 100 |
| RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 114 on average | 51 / 225 |
| 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 87 on average | 38 / 700 |
| RustSpain.com | EU Main | EU · groups of 12+ · weekly · 87 on average | 6 / 200 |
| CSL Scenery Budget Test | groups of 8+ · 85 on average | 0 / 500 |
Quick answers
from the figures on this pageWipe data
When does TESTING wipe?
No next wipe can be predicted for TESTING, which wipes at irregular times. On Thursday 5 November at 19:00 UTC the monthly force wipe arrives and every Rust server wipes. 10 days 5 hours ago the current world was made.
On TESTING, what happens on wipe day?
Recent wipes averaged a busiest count of 15 players. 0 hours after the latest wipe the crowd peaked. Recent wipes held the crowd above half that peak until the next wipe in 80% of cases. The fall below half arrived by day 1 when it didn't hold.
Server
Which location hosts TESTING?
A region is not published by TESTING. A server's stated location is what Rust Server Analytics shows; where the machine stands is not looked up. 51.83.150.41:28015 is its address.
Which Rust version is TESTING on?
The platform is Windows, with Rust network protocol 2635 and build 168909 running on TESTING. Joining requires the same protocol on your game; Steam handles the update.
What uptime does TESTING show, and is it up?
As of the latest refresh, TESTING is online. About 2 days 4 hours ago is when it last restarted, judged by its reported uptime. Uptime over the last full days (7) was 76%, or 127 of 168 hours. 13 September 2026 is when Rust Server Analytics first recorded it.
What performance does TESTING show?
Server fps averaged 128 over the last 48 hours, with a floor of 125. Entity count reached 4,021, covering buildings, deployables and the rest of the world. Peak memory was 1,054 MB. Players experience lag as low fps combined with a rising entity count.
Tags
Which meanings do the tags on TESTING carry?
The game's server browser reads the tags TESTING publishes: gmrust (Game mode): Survival in the standard Rust format; mp500 (Max players): 500 slots in total; ts8 (Group limit): The game default applies: 8 per team at most; v2635 (Protocol): Protocol 2635 is required: your game must match to connect; cs168909 (Build): The game build is 168909; ptrak (Networking): It uses RakNet, the standard network layer for the game; $r? (Region code): A region code is not set; ^z (Modded): Plugins or settings change the game, so it sits under Modded; ^y (Carbon): Plugin framework: Carbon. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
Where does TESTING appear across Rust Server Analytics's lists and filters?
These Rust Server Analytics lists include TESTING: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
Player numbers
Against other Rust servers, how does TESTING compare?
The seven-day player-hours rank for TESTING is #8,845, inside the top 40% of all ranked servers.
What is the population of TESTING?
Of 500 slots, 0 are filled on TESTING at this refresh. Seven-day figures: an average of 0 players and a peak of 4. Across the last 48 hours, 09:00 UTC shows the highest average: 0 players.
Settings
How is TESTING configured, and what rules apply?
No gather rate is given in the name of TESTING. The game's default 8-player group limit is in force. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. In the server browser it sits under Modded, where plugins or settings alter the game. Carbon plugins are run. Anti-cheat status: VAC on.
The map on TESTING: which one is it?
TESTING uses a procedural map of size 1,000 with seed 612351, generated by the game. The map is reproducible from its size and seed and can be seen on RustMaps from here.
Connection
What is the way onto TESTING?
Use Launch Rust on this page to open Rust through Steam and connect, or start Rust, press F1 and enter client.connect 51.83.150.41:28015.