testing
Offline 185.189.255.249:35400 checked 29d 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 20 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Li4Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Bx1Wipe schedule
from its schedule tagNext wipe Tuesday 3 November, 11:31 UTC, in 4d 15h. Its weekly schedule tag · low confidence
Coming wipes
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.
Bx2Wipes
newest first · each peak a flare-up, on one √ span to its biggest| 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.
Bx6Similar servers
the same kind of game, then region, group limit, rate and wipesLogQuick answers
from the figures on this pageWipe schedule
What does wipe day look like on testing?
At their busiest, its recent wipes averaged 2 players. 1 hours into the latest wipe, player numbers topped out. Above half the peak until the next wipe: that held in 100% of its recent wipes.
What is the wipe schedule on testing?
Too few wipes are recorded on testing to confirm its schedule; the tag is what the prediction follows. Tuesday 3 November at 11:31 UTC is when its next wipe is due. The world it runs now dates from 30 days 8 hours ago. Its tags carry a weekly wipe schedule.
Player counts
How busy is testing?
The last time testing was seen was 29 days 4 hours ago, and it is offline now.
How does testing rank against other Rust servers?
The top 70% of ranked servers includes testing, at #16,773 for player hours over the last seven days.
Map and rules
Which map does testing run?
testing runs a procedural map of size 2,500 with seed 53296983, generated by the game. From this page you can view the map on RustMaps, since the same size and seed give the same map.
What are the rules and settings on testing?
The name testing does not specify a gather rate. The group limit is 5 players. The server runs survival, standard play: gathering, building and raiding. Combat between players and raiding are both possible. Plugins or settings change the game, and it is listed under Modded in the server browser. Oxide plugins are in use. The server has VAC, Valve's anti-cheat, turned on.
About the server
Which version of Rust does testing run?
The build on testing is Rust network protocol 2633 and build 165217, running on Windows. To join, your game must match the protocol; Steam handles the update.
Is testing online, and how reliable is it?
Last seen 29 days 4 hours ago, testing is offline right now. It was up 0 of 168 hours across the last 7 full days, or 0% of the time. The first record of it on Rust Heatmap is 20 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. To connect, use 185.189.255.249:35400.
Lists and filters
Which Rust Heatmap lists and filters include testing?
The Rust Heatmap lists that testing fits are: Modded Rust servers, by live population. Filtering the list by Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly brings it up.
What do the server tags on testing mean?
The game's server browser reads the tags testing publishes: gmvanilla (Game mode): The vanilla survival game; mp50 (Max players): Slot count: 50; ts5 (Group limit): The team limit is 5; v2633 (Protocol): To join, run the same version: game protocol 2633; cs165217 (Build): The game build here is 165217; ptrak (Networking): The network layer is RakNet, the game's standard one; $r? (Region code): The region code is blank; ^w (Weekly): A wipe every week; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Settings or plugins alter the game, which puts it under Modded. The top of this page also shows the tags for players now, the queue and when the world was made.
How to join
How do I join testing?
Press F1 in Rust to open the console, then enter client.connect 185.189.255.249:35400. Alternatively, join from this page with Launch Rust: it opens Rust through Steam and connects you.