A quiet classroom so far: 1 of 10 on average. Plenty of space to grow.
Standingrank on player hours
74/ 100
B−
Holds a respectable place: #5,755 on player hours.
Uptimehours on the list, last 48
4/ 100
F
Attendance needs work: on the list only 2 of the last 48 hours.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
67/ 100
C+
Keeps a fair share of its players through a wipe: 67% of wipes kept half their crowd.
Momentumrank now against a week ago
55/ 100
C−
Moving up: up 557 places this week.
A term to build on.
Strongest in standing (B−); uptime is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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 best
RankRank in region
Top 26% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·W·····
······W
······W
·······
····WW·
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no 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 gap9.4 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held67%else halves by day 9
The first 48 hours of its last wipes
Sat 24 OctFri 23 OctSun 11 Oct
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
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is Dev Testing Server - Unsecure?
Dev Testing Server - Unsecure leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 45.129.156.2:28015.
How dependable is Dev Testing Server - Unsecure, and is it online at the moment?
At this moment, Dev Testing Server - Unsecure is offline; the last time it was seen was 35 hours ago. For the last 7 full days, it was up 38 of 168 hours, or 23% of the time. On 20 September 2026, Rust Server Score saw it for the first time.
On what Rust version does Dev Testing Server - Unsecure sit?
The server Dev Testing Server - Unsecure is on Rust network protocol 2635 and build 168909 under Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe schedule
When does Dev Testing Server - Unsecure wipe, and how often?
Dev Testing Server - Unsecure wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 3 days 14 hours.
What should you expect from wipe day on Dev Testing Server - Unsecure?
The average peak on its recent wipes was 1 players. Peak numbers came 0 hours into the latest wipe. Above half the peak until the next wipe: that was the pattern in 67% of its recent wipes. Day 9 is when it sank below half in the wipes that did not hold.
Player count
What position does Dev Testing Server - Unsecure hold in the rankings?
In the top 26% of all ranked servers, Dev Testing Server - Unsecure sits at #5,755 for player hours over the last seven days.
How many players does Dev Testing Server - Unsecure usually have?
Dev Testing Server - Unsecure is offline at the moment; the last time it was seen was 35 hours ago. The seven-day average is 1 players, with a peak of 1. Over the last 48 hours, the peak hour was 15:00 UTC, averaging 1 players.
Tags and filters
What is meant by the tags on Dev Testing Server - Unsecure?
gmrust (Game mode): Rust survival, played by the standard rules; mp10 (Max players): Its slot count is 10; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2635 (Protocol): To get in, your game needs to be on the same version: the protocol is 2635; cs168909 (Build): This runs on build 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here are the tags Dev Testing Server - Unsecure publishes, and the game's server browser reads them. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Which Rust Server Score filters and lists feature Dev Testing Server - Unsecure?
Rust Server Score lists that include Dev Testing Server - Unsecure: Best community servers, graded. It shows under the following filters 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.
Server rules
What settings and rules apply on Dev Testing Server - Unsecure?
Nothing in the name of Dev Testing Server - Unsecure states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. The server browser lists it under Community, as a community server. VAC, Valve's anti-cheat, is not enabled.
Which map is in play on Dev Testing Server - Unsecure?
A procedural map, generated by the game, is what Dev Testing Server - Unsecure runs.
How to join
How should you connect to Dev Testing Server - Unsecure?
Enter client.connect 45.129.156.2:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp10,ptrak,$r?,v2635,gmrust,cs168909,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp10
Max playersIts slot count is 10.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2635
ProtocolTo get in, your game needs to be on the same version: the protocol is 2635.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
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.
A term to build on. Strongest in standing (B−); uptime is the one to work on (F).