testing
Offline 185.189.255.249:35400 checked 29d ago
Server instruments
no direct query in 48 hoursPlayers now
0% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
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 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
- WPT 1Tue 3 Nov, 11:31 UTC4d 15h
- WPT 2Thu 5 Nov, 19:00 UTC6d 22hFW
- WPT 3Tue 10 Nov, 11:31 UTC11d 15h
- WPT 4Tue 17 Nov, 11:31 UTC18d 15h
- WPT 5Tue 24 Nov, 11:31 UTC25d 15h
- WPT 6Tue 1 Dec, 11:31 UTC32d 15h
- WPT 7Thu 3 Dec, 19:00 UTC34d 22hFW
- WPT 8Tue 8 Dec, 11:31 UTC39d 15h
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- 162/280
- 2/200
- 0/200
- 234/300
- 140/150
- 10/200
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on testing?
The busiest point of its recent wipes drew 2 players on average. 1 hours after the wipe, the crowd peaked on the latest wipe. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.
How often does testing wipe, and when?
Its tag guides the prediction: too few of testing's wipes are on record to confirm its schedule. On Tuesday 3 November at 11:31 UTC its next wipe is due. The world it runs now was made 30 days 8 hours ago. Its tags carry a weekly wipe schedule.
Lists and filters
Which tags does testing carry, and what do they mean?
Tags published by testing, read by the game's server browser: gmvanilla (Game mode): Survival on vanilla settings; mp50 (Max players): The server holds 50 slots; ts5 (Group limit): Teams are capped at 5; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): Game build reading: 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty; ^w (Weekly): Check: wipe cycle. Every week; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Modded: plugins or settings depart from the stock game. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.
Where does testing appear in Rust Metrics lists and filters?
On Rust Metrics, testing sits in these lists: Modded Rust servers, checked live. Reading: server list filters. It comes up under Type: Modded; Server tag: Weekly ^w, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Weekly.
Player count
Where does testing sit in the rankings?
Ranking for testing: #16,773 on seven-day player hours, top 70% of all ranked servers.
What is the population on testing?
Status for testing: offline. Last seen 29 days 4 hours ago.
Server details
Which location does testing run from?
No region tag on testing. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 185.189.255.249:35400.
What Rust version is testing on?
Rust network protocol 2633 and build 165217 on Windows is the build testing runs. Matching protocol is required to join. Let Steam update your game.
What is the uptime on testing, and is it online?
Reading: offline. testing last answered 29 days 4 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 20 September 2026.
Map and rules
What settings and rules apply on testing?
Reading the name gives no gather rate for testing. Group size, maximum: 5 players. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. The server browser lists it as Modded, where plugins or settings change how the game plays. Oxide plugins are running. Anti-cheat reading: VAC on, Valve's system.
Which map is live on testing?
Check: map. Procedural, size 2,500, seed 53296983, generated by the game on testing. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.
Join
What do you do to join testing?
To join: start Rust, press F1 and type client.connect 185.189.255.249:35400. Or press Launch Rust here and Steam opens the game and connects you.