Statistical profileOffline
Dev Testing Server - Unsecure
45.129.156.2:28015 checked 1d ago
Connect to this server
1. Main points
Players now
1/ 10
10% full
7-day average
1
peak 1
Rank
#5,759
top 26%
Last wipe
3d ago
no schedule published
Next wipe
–
no rhythm it keeps
Main points
- The server is offline; at its last check there were 1 players on it, 10% of its 10 slots.
- Over the last seven days it averaged 1 players, with a peak of 1.
- It ranks #5,759 of all ranked servers, the top 26%, on player hours over the last seven days.
- Its current map went up 3d ago.
2. Players
Figure 1: Players on Dev Testing Server - Unsecure
Players now and over time, UTC
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Source: Live server queries, Rust Census
3. Server performance
Figure 2: Frame rate, entities and memory
From asking the server directly; low fps and a climbing entity count mean lag
Note
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.
4. Rank
Figure 3: Rank among all servers, daily
1 is best
Top 26% of all ranked servers. Ranked on player hours over the last seven days.
Source: Live server queries, Rust Census
5. Wipe schedule
Patternno rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
Usual gap
9.4 days
between real wipes
On rhythm
0%
of its recent wipes
Wipe-day peak
1
players, last three wipes
Crowd held
67%
else halves by day 9
Figure 4: The first 48 hours of its last wipes
Players each hour, from the hour of the wipe
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Source: Live server queries, Rust Census
6. Wipes
Table 1: Wipes, newest first
Every wipe seen on this server
| 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 |
Notes
- 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.
Source: Live server queries, Rust Census
7. Map
Figure 5: Map of Dev Testing Server - Unsecure
Table 2: The world
As the server publishes it
| Map | Procedural Map |
|---|---|
| Size | – |
| Seed | – |
8. Server characteristics
Table 3: Characteristics of Dev Testing Server - Unsecure
What the server publishes and what was recorded
| Address | 45.129.156.2:28015 |
|---|---|
| Region | – |
| Max players | 10 |
| Group limit | 8, the default |
| Wipe schedule | – |
| Last wipe | 24 Oct 2026, 15:29 UTC |
| Hostname | – |
| First seen | 20 Sep 2026 |
9. Similar servers
Table 4: Servers like this one
The same kind of game, then region, group limit, rate and wipes
| Server | Characteristics | Players |
|---|---|---|
| Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 540 on average | 600 / 575 |
| Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 376 / 400 |
| Rustoria.co - EU Main | EU · groups of 16+ · weekly · 312 on average | 37 / 250 |
| Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 311 on average | 47 / 250 |
| Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 272 on average | 159 / 200 |
| Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 265 on average | 84 / 100 |
10. Quick answers
From the figures on this page.
Wipe schedule
On what schedule are wipes carried out on Dev Testing Server - Unsecure?
Wipes on Dev Testing Server - Unsecure fall at irregular times, leaving no next date to predict. A force wipe takes place monthly for every Rust server, with the next on Thursday 5 November at 19:00 UTC. This world was generated 3 days 19 hours ago.
What should you expect on wipe day at Dev Testing Server - Unsecure?
Recent wipes drew an average peak of 1 players. 0 hours after the latest wipe, the crowd peaked. The crowd stayed above half that peak until the next wipe in 67% of recent wipes. In the other cases, half the peak was lost by day 9.
Server details
How reliable is Dev Testing Server - Unsecure, and is it online now?
Dev Testing Server - Unsecure is offline at the time of this release; it was last seen 39 hours ago. 38 of 168 hours on across the last 7 full days gives an uptime of 23%. It was first seen by Rust Census on 20 September 2026.
In which location is Dev Testing Server - Unsecure based?
No region is published by Dev Testing Server - Unsecure. Where a server says it is is what Rust Census shows; where the machine stands is not looked up. At 45.129.156.2:28015 it is addressed.
On which Rust version does Dev Testing Server - Unsecure operate?
The version in use on Dev Testing Server - Unsecure is Rust network protocol 2635 and build 168909 on Windows. The same protocol is required for your game to join, and Steam updates it for you.
Population
How many players does Dev Testing Server - Unsecure carry?
Dev Testing Server - Unsecure is offline at present; its last recording was 39 hours ago. This release records a seven-day average of 1 players and a peak of 1. An average of 1 players was recorded at 15:00 UTC, the busiest hour of the last 48.
What position does Dev Testing Server - Unsecure hold in the server rankings?
For seven-day player hours, Dev Testing Server - Unsecure is ranked #5,759, placing it in the top 26% of all ranked servers.
Tags, lists
On Rust Census, which lists and filters carry Dev Testing Server - Unsecure?
The Rust Census lists that Dev Testing Server - Unsecure fits are: Community servers. Under these filters it comes 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.
Which meanings do the tags on Dev Testing Server - Unsecure carry?
Read by the game's server browser, Dev Testing Server - Unsecure publishes these tags: gmrust (Game mode): The game mode is standard survival as Rust runs it; mp10 (Max players): Slots: 10; ts8 (Group limit): 8 per team, which is the game's default limit; v2635 (Protocol): To connect, your game version must match protocol 2635; cs168909 (Build): Build 168909 is installed; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server carries no region code. Current players, queue length and world creation time are in the tags as well, and are shown at the top of this page.
Settings and map
What map is listed for Dev Testing Server - Unsecure?
The game generates the procedural map on Dev Testing Server - Unsecure.
On Dev Testing Server - Unsecure, what rules and settings are in force?
No gather rate is given in the name of Dev Testing Server - Unsecure. The default applies: groups are capped at 8 players. It runs survival, the standard game: gather, build, raid. Combat between players and raiding are both permitted. Community is its section in the server browser. The server does not run VAC, Valve's anti-cheat.
Connecting
What steps are needed to join Dev Testing Server - Unsecure?
Enter client.connect 45.129.156.2:28015 in Rust's console, opened with F1. Alternatively, use Launch Rust and join here: Steam opens the game and connects you.
11. Server tags
What each tag this server publishes means: a glossary.
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust | Game mode The game mode is standard survival as Rust runs it. |
|---|---|
mp10 | Max players Slots: 10. |
ts8 | Group limit 8 per team, which is the game's default limit. |
v2635 | Protocol To connect, your game version must match protocol 2635. |
cs168909 | Build Build 168909 is installed. |
ptrak | Networking The network layer is RakNet, the game's standard. |
$r? | Region code This server carries no region code. |
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.