Offline 83.17.151.145:28015 checked 20d ago
3am17 staging test
Connect
srv = rust.server("83.17.151.145:28017")
print(srv.connect_command)Right now
srv.summary()Players
srv.players.plot(range="48h")Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")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
srv.rank.plot(invert=True) # 1 is bestTop 62% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · too few wipes seen yet
srv.wipe_schedule()Not enough wipes seen yet to tell when the next one is. 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
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 8 Oct, 10:21 UTC20d ago | 1 | NaN | running | 1 |
| 1 | Sun 4 Oct, 09:42 UTC24d 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.
display(srv.map, srv.info())Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 83.17.151.145:28015
- region
- –
- max players
- 20
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 8 Oct 2026, 10:21 UTC
- hostname
- –
- first seen
- 3 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 552 on average | 636/675 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 485/525 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 299 on average | 59/250 |
| 3 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 298 on average | 36/250 |
| 4 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 270 on average | 138/200 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 256 on average | 255/300 |
Quick answers
From the figures on this page.
Population
What position does 3am17 staging test take in the server rankings?
Over the last seven days 3am17 staging test sits at #13,672 on player hours, in the top 62% of ranked servers.
How many players does 3am17 staging test hold at once?
3am17 staging test returns no live count at this refresh, having last been seen 20 days 8 hours ago.
Server facts
Which Rust version is 3am17 staging test on?
The build is Rust network protocol 2634 and build 166655 on Windows, run by 3am17 staging test. The protocol has to match before you can join, and Steam does the updating.
How reliable is 3am17 staging test, and is it up?
Offline now for 3am17 staging test, last seen 20 days 8 hours ago. 0 of 168 hours up over the last 7 full days, or 0%. Its earliest recorded date in Rust Data is 3 October 2026.
Which location does 3am17 staging test run from?
For 3am17 staging test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 83.17.151.145:28015 is its address.
Rules, settings, map
Which rules apply on 3am17 staging test, and what settings?
You will not find a gather rate in the string 3am17 staging test. No custom cap; the default of 8 players per group stands. Recorded as survival, gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. Anti-cheat status: VAC on.
Which map has 3am17 staging test loaded?
3am17 staging test runs a procedural map, which the game generates.
Wipes and dates
On what schedule does 3am17 staging test wipe?
The record for 3am17 staging test holds too few wipes to show a rhythm. On Thursday 5 November at 19:00 UTC the next monthly force wipe runs, and no Rust server is exempt. This world was created 20 days 9 hours ago.
On 3am17 staging test, what happens on wipe day?
Recent wipes averaged 1 players at their peak. 0 hours after the latest wipe, the crowd reached its peak. The crowd stayed above half that peak until the next wipe in 0% of recent wipes. Otherwise the crowd fell below half by day 1.
Tags and filters
Where does 3am17 staging test appear among Rust Data lists and filters?
On Rust Data, 3am17 staging test appears in these lists: Rust community servers, unfiltered. Under these filters on the server list, it is listed: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Which meanings do the tags on 3am17 staging test hold?
Read by the game's server browser, the tags 3am17 staging test publishes are: gmrust (Game mode): Rust survival in its standard form; mp20 (Max players): Slot count: 20; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166655 (Build): Recorded game build: 166655; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Connecting
What is the way into 3am17 staging test?
Enter client.connect 83.17.151.145:28015 in the console (F1 in Rust). Or press Launch Rust here, which opens Rust through Steam and makes the connection.