Rust PopulationField survey · Rust servers
Observing 61,286 players 11,755 servers 3,487 with someone on 128 fresh wipes in 3 h counted every five minutes
‹ All serversspecimen record
Specimen recordcat. no. 13,672habitat unknownfirst seen 3 Oct 2026

3am17 staging test

Offline 83.17.151.145:28015 checked 19d ago

Measurements

Players now
1/ 20
= 1 player
5% full
7-day average
0
peak –
Rank
#13,672
top 62%
Last wipe
19d ago
no schedule published
Next wipe
–
too few wipes seen yet
Obs. 1 · sightings

Players

No hourly history yet.

Hourly average and peak, UTC.

Obs. 2 · condition

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Obs. 3 · standing

Rank

daily · 1 is best
RankRank in region
15k10k15k20k3 Oct5 Oct8 Oct10 Oct13 Oct15 Oct

Top 62% of all ranked servers. Ranked on player hours over the last seven days.

Obs. 4 · the wipe cycle

Wipe schedule

too few wipes seen yet

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

4 days
usual gap
between real wipes
1
wipe-day peak
players, last three wipes
0%
crowd held
else halves by day 1

The first 48 hours of its last wipes

Thu 8 OctSun 4 Oct
00.250.50.751+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.

Log · wipes seen

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Thu 8 Oct, 10:21 UTC19d ago 1 – running 1
Sun 4 Oct, 09:42 UTC23d ago 1 halved by day 1 4 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.

Field questions

Quick answers

from the figures on this page

Population

How does 3am17 staging test rank against other Rust servers?

The last seven days of player hours place 3am17 staging test at #13,672, within the top 62% of all ranked servers.

How busy is 3am17 staging test?

At this count 3am17 staging test is offline, with its last sighting 19 days 11 hours ago.

Lists and tags

What do the server tags on 3am17 staging test mean?

The game's server browser reads the tags 3am17 staging test publishes: gmrust (Game mode): The game mode is standard Rust survival; mp20 (Max players): 20 slots are available; ts8 (Group limit): 8 per team is the default limit; v2634 (Protocol): The protocol is 2634; a different version will not connect; cs166655 (Build): The game build is 166655; ptrak (Networking): The network layer is RakNet, the game's standard; $r? (Region code): This server has no region code. The tags also carry the current player count, the queue and when the world was made; you will find them at the top of this page.

Which Rust Population lists and filters include 3am17 staging test?

3am17 staging test appears among the Rust Population lists that follow: Community servers, field-listed. Look for it under these filters on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Wipe schedule

What does wipe day look like on 3am17 staging test?

Across its recent wipes the busiest crowds averaged 1 players. Peak came 0 hours into the latest wipe. Half that peak held until the next wipe in 0% of its recent wipes. In those that did not hold, the fall below half came by day 1.

What is the wipe schedule on 3am17 staging test?

The record holds too few of 3am17 staging test's wipes to show a rhythm. The next monthly force wipe is on Thursday 5 November at 19:00 UTC; all Rust servers wipe then, this one too. 19 days 12 hours ago the current world was made.

Map and rules

Which map does 3am17 staging test run?

3am17 staging test uses a map the game generates: procedural.

What are the rules and settings on 3am17 staging test?

The name tells you nothing about gather rates: 3am17 staging test states none. The group limit is 8 players, which is the default. This server runs survival, gather, build and raid, as in the standard game. You can raid and fight other players here. You will find it under Community: it is a community server. You play with Valve's anti-cheat on: VAC.

About the server

Which version of Rust does 3am17 staging test run?

On Windows, 3am17 staging test runs Rust network protocol 2634 and build 166655. Steam updates your game automatically, but you need the same protocol to join.

Is 3am17 staging test online, and how reliable is it?

Offline at the moment, 3am17 staging test was last seen 19 days 11 hours ago. Over the last 7 full days, 0 of 168 hours were online, or 0%. On 3 October 2026, Rust Population saw it for the first time.

Where is 3am17 staging test located?

Nothing published by 3am17 staging test states a region. The location a server claims is what Rust Population shows, not the place where the machine stands. 83.17.151.145:28015 is where it lives.

Getting in

How do I join 3am17 staging test?

Open the console with F1 in Rust and enter client.connect 83.17.151.145:28015. Joining from this page with Launch Rust works too, opening Rust through Steam and connecting you.

Key to its markings

Server tags

what each one means

Published as mp20,ptrak,$r?,v2634,gmrust,cs166655,ts8

Game

gmrust
Game mode The game mode is standard Rust survival.
mp20
Max players 20 slots are available.
ts8
Group limit 8 per team is the default limit.
v2634
Protocol The protocol is 2634; a different version will not connect.
cs166655
Build The game build is 166655.
ptrak
Networking The network layer is RakNet, the game's standard.
$r?
Region code This server has 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.