TESTING
Online 51.83.150.41:28015 checked 11m ago
Vital stats
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
Top 40% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Its 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
| 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.
Tags
Which Rust Pop Watch lists and filters include TESTING?
These are the Rust Pop Watch lists that include TESTING: Modded Rust servers, live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 2 weeks.
What do the server tags on TESTING mean?
These are the tags TESTING publishes for the browser: gmrust (Game mode): Survival, standard Rust style; mp500 (Max players): It has 500 slots; ts8 (Group limit): This uses the default limit of 8 players per team; v2635 (Protocol): You need the same game version to get in: protocol 2635; cs168909 (Build): The game build is 168909; ptrak (Networking): The network layer is RakNet, which is the game's standard; $r? (Region code): Region code left blank; ^z (Modded): The game is changed by plugins or settings, hence the Modded listing; ^y (Carbon): A plugin framework called Carbon is running here. The tags also carry its current players, queue and world creation time, all shown at the top of this page.
Population
How does TESTING rank against other Rust servers?
A seven-day player-hours placing of #8,848 puts TESTING in the top 40% of all ranked servers.
How many players are on TESTING right now?
TESTING is holding 0 players, with 500 slots in total. Peak for the week was 4, against an average of 0 players. Over the last 48 hours, the fullest hour was 09:00 UTC, averaging 0 players.
Server details
Is TESTING online, and how reliable is it?
TESTING is live at the moment. Based on the uptime it reports, the last restart was about 2 days 5 hours ago. The last 7 full days saw uptime of 76%, with 127 out of 168 hours online. Rust Pop Watch's first record of it is 13 September 2026.
Does TESTING run smoothly?
The 48-hour average was 128 server fps, with a low of 125. Entities reached a maximum of 4,021: buildings, deployables and everything else. Up to 1,054 MB of memory was used. What players experience as lag comes from low fps and a rising entity count.
Where is TESTING located?
There is no region from TESTING. Rust Pop Watch does not look up where the machine stands; it shows where a server says it is. Connect at 51.83.150.41:28015.
Which Rust version is TESTING on?
On Windows, TESTING runs Rust network protocol 2635 and build 168909. Steam updates your game so it matches the protocol needed to join.
The wipe schedule
What happens on TESTING when wipe day comes around?
Across its recent wipes, the busiest point averaged 15 players. 0 hours after the latest wipe, the crowd hit its peak. Its recent wipes kept the crowd above half the peak until the next one 80% of the time. In the wipes that didn't hold, the crowd sank below half by day 1.
What is the wipe schedule on TESTING?
No next wipe can be predicted for TESTING: its wipes happen at irregular times. A force wipe comes round every month for all Rust servers, with the next on Thursday 5 November at 19:00 UTC. 10 days 6 hours is when the present world was made.
Rules and settings
Which map does TESTING run?
The procedural map on TESTING measures 1,000 and comes from the game with seed 612351. Matching size and seed produce the same map, so RustMaps can show it from this page.
What are the rules and settings on TESTING?
Nothing in the name tells you the gather rate on TESTING. The group limit is 8 players, the game's default. the usual game of gathering, building and raiding: that is the survival mode. Fighting and raiding between players is allowed. Plugins or settings alter the game, and the browser lists it as Modded. The plugin count is Carbon. Anti-cheat is on: VAC, Valve's system.
Getting in
How do I join TESTING?
Enter client.connect 51.83.150.41:28015 in the console after pressing F1 in Rust. Or use Launch Rust here to open Rust through Steam and connect automatically.