TESTING
Online 51.83.150.41:28015 checked 10m ago
Server instruments
last reading Tue 20:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 125 · below 20 is lag, below 10 is badEntities
48 h range 1,764–4,038 · memory 893 MBUptime
2 days 1 hours since its last restart, at the last readingPlayers
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 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- 137/500
- 124/100
- 127/225
- 29/200
- 124/700
- 38/1000
Quick answers
from the figures on this pageReset cycle
What should you expect from wipe day on TESTING?
At their busiest, its recent wipes drew 15 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. Until the next wipe, the crowd stayed above half that peak in 80% of its recent wipes. By day 1 it fell below half when it didn't.
What wipe timing does TESTING follow?
There is no next wipe to predict: TESTING wipes at irregular times. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 10 days 2 hours ago.
Tag meanings
Which tags does TESTING carry, and what do they mean?
Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): Slots: 500; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Modded: plugins or settings depart from the stock game; ^y (Carbon): Check: framework. Carbon from TESTING. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Which lists and filters on Rust Metrics show TESTING?
Rust Metrics lists featuring TESTING: Modded Rust servers, checked 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.
Population
Where does TESTING sit in the rankings?
Ranking for TESTING: #8,822 on seven-day player hours, top 40% of all ranked servers.
What player count does TESTING carry?
Current headcount on TESTING: 0 players, 500 slots available. Seven-day check: 0 players on average. Peak reading: 4. Average at the busiest hour was 0 players, at 09:00 UTC over the last 48 hours.
Operator and location
Where does TESTING sit?
No region comes from TESTING. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 51.83.150.41:28015.
What Rust version is TESTING on?
Reading: TESTING, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.
How does TESTING perform?
Over the last 48 hours the average was 128 server fps; the floor was 125. Peak entity count: 4,038. Buildings, deployables and all else included. Memory peak: 1,054 MB. Expect lag when fps falls and entities climb.
Is TESTING up, and how often does it stay up?
Reading: online. TESTING answers right now. By its reported uptime, the last restart was roughly 2 days 1 hours ago. Uptime for the last 7 full days: 103 of 168 hours, or 61%. Reading: first seen 13 September 2026, recorded by Rust Metrics.
Map and rules
What settings and rules apply on TESTING?
Reading the name gives no gather rate for TESTING. 8 players per group, the default value. The mode is survival. Note the following: the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Modded. Plugins or settings change the game. Check: plugins. It runs Carbon of them. VAC is on. That is Valve's anti-cheat.
What map is TESTING on?
Check: map. Procedural, size 1,000, seed 612351, generated by the game on TESTING. The map repeats when size and seed match. Open it on RustMaps from this page.
Connection
How do you connect to TESTING?
Press F1 in Rust and enter client.connect 51.83.150.41:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.