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 8% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
fixed weekdaysNext wipe Monday 19 October, 14:59 UTC, in 1d 5h. Every Monday at 14:59 and every Thursday at 14:58 UTC · high confidence
Coming wipes
- 1d 5hMon 19 Oct, 14:59 UTC
- 4d 5hThu 22 Oct, 14:58 UTC
- 8d 5hMon 26 Oct, 14:59 UTC
- 11d 5hThu 29 Oct, 14:58 UTC
- 15d 5hMon 2 Nov, 14:59 UTC
- 18d 9hThu 5 Nov, 19:00 UTCFW
- 22d 5hMon 9 Nov, 14:59 UTC
- 25d 5hThu 12 Nov, 14:58 UTC
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 18, 4 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Sat 17 Oct, 19:12 UTC13h ago | – | – | running | 0 |
| Thu 15 Oct, 14:58 UTC2d ago | 18 | held half | 2.2 days | 3 |
| Mon 12 Oct, 14:59 UTC5d ago | 25 | held half | 3 days | 0 |
| Thu 8 Oct, 14:58 UTC9d ago | 12 | held half | 4 days | 4 |
| Mon 5 Oct, 15:00 UTC12d ago | 24 | held half | 3 days | 2 |
| Thu 1 Oct, 17:57 UTC FW16d ago | 23 | halved by day 1 | 3.9 days | 1 |
| Mon 28 Sep, 15:58 UTC19d ago | 24 | held half | 3.1 days | 2 |
| Fri 25 Sep, 17:03 UTC22d ago | 22 | held half | 3 days | 2 |
| Mon 21 Sep, 15:57 UTC26d ago | 6 | halved by day 1 | 4 days | 0 |
| Mon 14 Sep, 15:56 UTC33d 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
- 17/ 100
- 259/ 400
- 181/ 225
- 129/ 100
- 312/ 1000
- 23/ 700
Quick answers
Tags and listings
Where does TESTING appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry TESTING are: Modded Rust servers. Its entry appears under the filters Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 24 hours.
How should you read the tags on TESTING?
The server browser shows these tags for TESTING: gmrust (Game mode): This is the standard Rust survival experience; mp500 (Max players): The slot count is 500; ts8 (Group limit): The default team size of 8 applies here; v2634 (Protocol): This server runs game protocol 2634, so your game must match that version to join; cs167781 (Build): The build number is 167781; ptrak (Networking): Standard RakNet networking; $r? (Region code): No region is set; ^z (Modded): You'll see it in Modded, since plugins or settings modify the game; ^y (Carbon): This server relies on Carbon for plugins. At the top of this page you will also find its current players, its queue and when its world was made — all from the tags.
Server details
What's the performance like on TESTING?
It averaged 101 server fps over the last 48 hours, with a low of 60. Buildings, deployables and all other world objects added up to as many as 76,155 entities. 2,922 MB was the highest memory it used. Players experience lag when fps drops and entities climb.
What's the location of TESTING?
TESTING does not put out a region. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. To connect, use 51.83.150.41:28015.
How reliable is TESTING?
Right now TESTING is online. The uptime it gives puts the last restart at roughly 11 hours ago. Over the past full 7 days it stayed up for 146 of 168 hours, or 87%. 13 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for TESTING?
Rust network protocol 2634 and build 167781 is what TESTING runs, on Windows. Steam handles the update; you just need your game on the matching protocol to join.
Wipe schedule
What schedule does TESTING follow for wipes?
TESTING follows a every Monday at 14:59 and every Thursday at 14:58 UTC wipe pattern. Monday 19 October at 14:59 UTC is when the next wipe is due. The world you are on now was created 13 hours.
What happens on wipe day at TESTING?
Across its recent wipes, the average busiest point drew 18 players. The peak crowd on the latest wipe came 4 hours in. Recent wipes kept the crowd above half that peak until the next wipe 80% of the time. It held on until day 1, then dipped below half.
Rules and settings
What settings are in place on TESTING?
No gather rate appears in the name of TESTING. 8 players is the group cap, the game's default. It runs survival, gather, build and raid, the standard game. Fighting and raiding between players is allowed. Plugins or settings change the game, so the browser lists it as Modded. Carbon plugins are running here. VAC is on: Valve's anti-cheat is active.
What's the map on TESTING?
A game-generated procedural map of size 1,000 with seed 612351 is in play on TESTING. You can see it on RustMaps from this page, since the same size and seed produce the same map.
Player count
How many players are on TESTING?
TESTING is holding 0 players on its 500 slots at the moment. The seven-day average is 4 players, with a peak of 33. Over the last 48 hours, 16:00 UTC drew the most players, 8 on average.
What position does TESTING hold in the server rankings?
For player hours in the last seven days, TESTING ranks #1,775, within the top 8% of ranked servers.
How to join
How do you get into TESTING?
Open Rust and press F1, then type client.connect 51.83.150.41:28015. Alternatively, click Launch Rust on this page to join via Steam.