testing
Offline 185.189.255.249:35400 checked 29d ago
Players
average and peak, with its wipes markedEvery five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
fps, entities and memory, from asking the server directly48 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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
from its schedule tagNext wipe Tuesday 3 November, 11:31 UTC, in 4d 15h. Its weekly schedule tag · low confidence
Coming wipes
| In | When, UTC | Kind |
|---|---|---|
| 4d 15h | Tue 3 Nov, 11:31 UTC | its own |
| 6d 22h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 11d 15h | Tue 10 Nov, 11:31 UTC | its own |
| 18d 15h | Tue 17 Nov, 11:31 UTC | its own |
| 25d 15h | Tue 24 Nov, 11:31 UTC | its own |
| 32d 15h | Tue 1 Dec, 11:31 UTC | its own |
| 34d 22h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 39d 15h | Tue 8 Dec, 11:31 UTC | its own |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Tue 29 Sep, 11:31 UTC30d ago | 1 | – | running | 1 |
| Sun 27 Sep, 07:47 UTC32d ago | 2 | held half | 2.2 days | 2 |
| Sat 26 Sep, 09:48 UTC33d ago | 2 | – | 0.9 days | 0 |
| Fri 25 Sep, 14:19 UTC34d ago | 2 | – | 0.8 days | 1 |
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| Server | Profile | Players now |
|---|---|---|
| RETRO RUST #3 Х5|MAX 5|LOOT+|CRAFT GLOBAL 29.10 | EU · groups of 5 · weekly · 75 on average | 176 / 280 |
| 红果十倍/10.26号新开/爆枪/新人入门 | EA · groups of 6 · weekly · 9 on average | 1 / 200 |
| РУССКИЙ ДЛЯ НОВИЧКОВ | MAX5 | 50%Upkeep 23.10 | EU · groups of 5 · weekly · 1 on average | 0 / 200 |
| Rusty Moose |EU Mini| | EU · groups of 5 · weekly · 74 on average | 231 / 300 |
| Rusty Moose |US Mini| | NA · groups of 5 · weekly · 56 on average | 132 / 150 |
| [LATAM] LUNARUST Vanilla | 27/10 Wipe | SA · groups of 5 · weekly · 17 on average | 11 / 200 |
Quick answers
from the figures on this pageWipe data
The wipe schedule for testing: what is it?
The tag sets the prediction: too few of testing's wipes are on record to confirm its schedule. A wipe is scheduled for Tuesday 3 November at 11:31 UTC, according to this server's cycle. The world now in play was created 30 days 8 hours ago. A weekly wipe schedule is published in its tags.
Wipe day on testing: what should you expect?
The average busiest count over recent wipes is 2 players. Peak population for the latest wipe came 1 hours after it began. The crowd stayed above half that peak until the next wipe in 100% of recent wipes.
Server details
In which region does testing sit?
No region is published by testing. Rust Server Analytics does not look up where the machine stands; it shows where a server says it is. The address of the server is 185.189.255.249:35400.
What Rust build does testing run?
On Windows, testing runs Rust network protocol 2633 and build 165217. Joining requires the same protocol on your game; Steam handles the update.
What uptime does testing show, and is it up?
Offline at this refresh: testing, last seen 29 days 3 hours ago. 0% uptime over the last 7 full days, equal to 0 of 168 hours. The first sighting of it by Rust Server Analytics was on 20 September 2026.
Lists and tags
What do testing's tags stand for?
The game's server browser reads the tags testing publishes: gmvanilla (Game mode): The vanilla survival format; mp50 (Max players): Capacity of 50 slots; ts5 (Group limit): Teams hold no more than 5; v2633 (Protocol): Protocol 2633 is required: your game must match to connect; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet is the network layer, the game's standard one; $r? (Region code): No region code has been set; ^w (Weekly): Wipes run on a weekly cycle; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings change the game, so it sits under Modded. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.
On Rust Server Analytics, which lists and filters feature testing?
These Rust Server Analytics lists include testing: Modded Rust servers: live data. On the server list, the filters that return it are: Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Population
Against other Rust servers, how does testing compare?
On player hours over seven days, testing ranks #16,773, within the top 70% of ranked servers.
At what level does testing run its population?
testing is offline at this refresh; the last contact was 29 days 3 hours ago.
Settings
What settings and rules does testing use?
Gather rate is not mentioned in the name of testing. The cap on group membership is 5 players. It runs survival, the standard game: gather, build, raid. Player-versus-player combat and raiding are both enabled. Plugins or settings modify the game, and it is listed as Modded. Plugins from Oxide are in use. The server runs with VAC, Valve's anti-cheat, enabled.
What is the map for testing?
A procedural map of size 2,500 with seed 53296983, generated by the game, runs on testing. The map is reproducible from its size and seed and can be seen on RustMaps from here.
How to join
How can a player join testing?
In the Rust console (F1), enter client.connect 185.189.255.249:35400. Launch Rust on this page also works, opening Rust through Steam and connecting you.