TESTING
Online 51.83.150.41:28015 checked 11m ago
Li2Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Li3Server 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.
Li4Rank
daily · 1 is bestTop 40% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe 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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe day
What does wipe day look like on TESTING?
Its recent wipes drew an average peak of 15 players. The crowd on the latest wipe reached its peak 0 hours in. The crowd stayed above half that peak until the next wipe in 80% of its recent wipes. In the wipes that did not hold, numbers dropped below half by day 1.
What is the wipe schedule on TESTING?
No next wipe can be predicted: TESTING wipes when it chooses, at irregular times. Thursday 5 November at 19:00 UTC is the next monthly force wipe, when every Rust server wipes. The world in play now was made 10 days 3 hours ago.
Population
How busy is TESTING?
The current population of TESTING is 0, against 500 slots. Averaged over the past week: 0 players, peaking at 4. Look at 09:00 UTC for the last 48 hours: that hour averaged 0 players.
How does TESTING rank against other Rust servers?
The top 40% of ranked servers includes TESTING, at #8,833 for player hours over the last seven days.
Map and rules
Which map does TESTING run?
TESTING runs a procedural map of size 1,000 with seed 612351, generated by the game. You can look at the map on RustMaps from this page: the same size and seed give the same map.
What are the rules and settings on TESTING?
A gather rate is not given in the name TESTING. Groups can contain up to 8 players, the default in the game. The server runs survival, gather, build and raid in the standard game. You can fight other players and raid their bases. In the server browser it is Modded, meaning plugins or settings modify the game. Plugin count: Carbon. The server has VAC, Valve's anti-cheat, turned on.
Location and uptime
Which version of Rust does TESTING run?
Rust network protocol 2635 and build 168909 is the build TESTING runs, on Windows. Steam updates your game for you, and the protocol has to match for you to join.
Is TESTING online, and how reliable is it?
Online now: TESTING. Its reported uptime dates the last restart to about 2 days 2 hours ago. It was up 103 of 168 hours across the last 7 full days, or 61% of the time. It first appears in Rust Heatmap records on 13 September 2026.
Where is TESTING located?
Nothing about a region comes from TESTING. What Rust Heatmap shows is where a server says it is. Where the machine stands is not looked up. 51.83.150.41:28015 is its address.
Does TESTING run smoothly?
Average server fps over the last 48 hours was 128; it never dropped below 125. Buildings, deployables and the rest of the world came to as much as 4,021 entities. At its peak it held 1,054 MB of memory. What players call lag is low fps together with a growing entity count.
Tags
Which Rust Heatmap lists and filters include TESTING?
These Rust Heatmap lists include TESTING: Modded Rust servers, by live population. These are the filters that return it on the 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?
The game's server browser reads the tags TESTING publishes: gmrust (Game mode): Survival in the standard Rust form; mp500 (Max players): This server has 500 slots; ts8 (Group limit): Teams cap at 8, which is the game default; v2635 (Protocol): The server runs game protocol 2635, so your game has to match it; cs168909 (Build): This build is 168909; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): A region code is not set; ^z (Modded): The game is changed by settings or plugins, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here. Players now, the queue and the world's creation time sit in the tags as well and appear at the top of this page.
How to join
How do I join TESTING?
To join by console, open it with F1 in Rust and enter client.connect 51.83.150.41:28015. Or press Launch Rust on this page, which connects you through Steam.