Server profile
TESTING
Online, with 0 of 500 players on; ranked #8,833 of every public Rust server, the top 40%. It last wiped 10d ago.
Online 51.83.150.41:28015 checked 12m ago
The crowd
Players
Who is on it, hour by hour and day by day.
Source: every five minutes, from the Steam server list.
Note: hourly average and peak, UTC.
Note: daily average and peak, UTC.
Under the hood
Server performance
Frames per second, entities and memory, asked of the server itself.
Note: 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.
The standings
Rank
Its place among every ranked server, day by day; 1 is best.
Note: Top 40% of all ranked servers. Ranked on player hours over the last seven days.
The wipe cycle
Wipe schedule
No rhythm it keeps.
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 wipesPlayers each hour, from the hour of the wipe
Note: players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
The record
Wipes
Every wipe we saw, 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 |
Note: 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.
If you like this one
Similar servers
The same kind of game, then region, group limit, rate and wipes.
The short version
Quick answers
From the figures on this page.
Wipe days
On TESTING, what happens on wipe day?
The average busiest point of its recent wipes was 15 players. 0 hours into the latest wipe, the crowd on the server reached its peak. Half the peak held until the next wipe in 80% of its recent wipes. In the other cases, it dropped below half by day 1.
On what schedule does TESTING wipe?
No next wipe can be predicted for TESTING, which wipes at irregular times. A force wipe falls on every Rust server once a month, and the next one is Thursday 5 November at 19:00 UTC. The world you are playing on now was made 10 days 4 hours ago.
Server details
Does TESTING hold a steady frame rate?
Server fps averaged 128 over 48 hours; the lowest reading was 125. Buildings, deployables and the rest took the entity count as high as 4,021. Memory use peaked at 1,054 MB. A climbing entity count and low fps are what players experience as lag.
Which Rust version is TESTING on?
The Rust build is network protocol 2635 and build 168909, running on Windows, for TESTING. Joining needs your game on the same protocol, which Steam updates for you.
How reliable is TESTING, and is it up at the moment?
TESTING is currently reachable and online. About 2 days 2 hours ago is when it last restarted, judged from the uptime it reports. The last 7 full days gave 103 of 168 hours up, or 61% of the time. Rust Insights first logged this server on 13 September 2026.
In which location does TESTING sit?
No region is published by TESTING. The location shown on Rust Insights is the one a server states, not a lookup of where the machine sits. You can reach it at 51.83.150.41:28015.
Server tags
What is meant by each tag on TESTING?
These tags come from TESTING and are read by the game's server browser: gmrust (Game mode): The game mode is standard Rust survival; mp500 (Max players): 500 slots in total; ts8 (Group limit): This is the game default: 8 per team at most; v2635 (Protocol): Matching versions are required, and the protocol is 2635; cs168909 (Build): It runs game build 168909; ptrak (Networking): RakNet handles the network layer, as it does by default; $r? (Region code): The region code field is empty; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): Carbon, a plugin framework, runs on this server. The tags also hold the current player count, the queue and when the world was created, all of which appear at the top of this page.
Where does TESTING turn up among the Rust Insights lists and filters?
The Rust Insights lists that carry TESTING are Modded Rust servers, explained. 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.
Player counts
What does the population of TESTING look like?
TESTING shows 0 players at the moment, against 500 slots. A weekly average of 0 players goes with a peak of 4. The busiest point of the last 48 hours fell at 09:00 UTC, averaging 0 players.
Where does TESTING sit in the rankings?
On player hours for the last seven days, TESTING sits at #8,833, inside the top 40% of ranked servers.
Map and rules
What settings and rules apply on TESTING?
No gather rate appears in the name of TESTING. No group limit is set, so the game's default of 8 players applies. You get survival as the game mode, the standard game: gather, build, raid. PvP and raiding are both enabled. It is a Modded entry: plugins or settings modify the game. Carbon is the plugin count it runs. The server has Valve's VAC anti-cheat switched on.
What is the map on TESTING?
The game generates the map on TESTING: procedural, size 1,000, seed 612351. Size and seed give the same map each time, so this page lets you look at it on RustMaps.
Connecting
What is the way to join TESTING?
To connect, start Rust and enter client.connect 51.83.150.41:28015 in the console (F1). Or join through Launch Rust on this page, which opens Rust via Steam and connects you.