Dev Testing Server - Unsecure
Offline 45.129.156.2:28015 checked 1d ago
Server instruments
no direct query in 48 hoursPlayers now
10% full 7-day avg7-day peakServer 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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 26% 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 24 Oct, 12:40 UTC3d ago | 1 | – | running | 1 |
| Fri 23 Oct, 13:08 UTC4d ago | 1 | – | 1 days | 1 |
| Sun 11 Oct, 13:35 UTC16d ago | 1 | held half | 12 days | 1 |
| Sun 4 Oct, 12:37 UTC23d ago | 1 | held half | 7 days | 0 |
| Tue 22 Sep, 19:01 UTC35d ago | 1 | halved by day 9 | 11.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- 247/275
- 20/250
- 17/250
- 163/200
- 64/200
- 37/100
Quick answers
from the figures on this pageWipe timing
What should you expect from wipe day on Dev Testing Server - Unsecure?
An average of 1 players came at the busiest on its recent wipes. Peak crowd on the latest wipe: 0 hours in. Above half that peak the crowd stayed until the next wipe in 67% of recent wipes. By day 9 it fell below half when it didn't.
How often does Dev Testing Server - Unsecure wipe, and when?
No next wipe can be predicted for Dev Testing Server - Unsecure, which wipes at irregular times. The next monthly force wipe, when every Rust server wipes, falls on Thursday 5 November at 19:00 UTC. The world it runs now was made 3 days 14 hours ago.
Tags
How should you read the tags on Dev Testing Server - Unsecure?
These are the tags Dev Testing Server - Unsecure publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp10 (Max players): 10 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.
Where does Dev Testing Server - Unsecure appear in Rust Metrics lists and filters?
Rust Metrics lists featuring Dev Testing Server - Unsecure: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last week.
Occupancy
What position does Dev Testing Server - Unsecure hold among Rust servers?
Player hours over seven days put Dev Testing Server - Unsecure at #5,755, in the top 26% of all ranked servers.
What player count does Dev Testing Server - Unsecure carry?
Reading for Dev Testing Server - Unsecure: offline at this moment; last seen 34 hours ago. Check: players over seven days. Average 1, peak 1. Check: 48-hour peak. 15:00 UTC, 1 players on average.
Operator and location
What location is Dev Testing Server - Unsecure hosted in?
No region tag on Dev Testing Server - Unsecure. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Check: address. It reads 45.129.156.2:28015.
What Rust version is Dev Testing Server - Unsecure on?
Reading: Dev Testing Server - Unsecure, Rust network protocol 2635 and build 168909, Windows. To get in, your game needs the same protocol; Steam applies the update.
What is the uptime on Dev Testing Server - Unsecure, and is it online?
Dev Testing Server - Unsecure reports offline. The last reading came 34 hours ago. Reading: 23% uptime over the last 7 full days. It was up 38 of 168 hours. The first sighting on Rust Metrics was 20 September 2026.
Settings and map
What settings and rules apply on Dev Testing Server - Unsecure?
Reading the name gives no gather rate for Dev Testing Server - Unsecure. The group cap is 8 players, which is the default in the game. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Combat and raiding against other players are on. Under Community in the server browser you will find it. Anti-cheat reading: VAC off, Valve's system.
What map is Dev Testing Server - Unsecure on?
The game generates a procedural map for Dev Testing Server - Unsecure.
How to join
How do you connect to Dev Testing Server - Unsecure?
Press F1 in Rust and enter client.connect 45.129.156.2:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.