Offline 45.83.145.30:28415 checked 22d ago
acceptance002
Connect
srv = rust.server("45.83.145.30:28417")
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 best
Top 71% 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 0, 0 hours in.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sun 4 Oct, 08:14 UTC23d ago | 0 | NaN | running | 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.
display(srv.map, srv.info())
Map
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 45.83.145.30:28415
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 4 Oct 2026, 08:14 UTC
- hostname
- –
- first seen
- 4 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 · 511 on average | 569/700 |
| 1 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 340 on average | 33/250 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 337 on average | 72/250 |
| 3 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 316 on average | 296/400 |
| 4 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 280 on average | 125/200 |
| 5 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 261 on average | 120/225 |
Quick answers
From the figures on this page.
Population
How does acceptance002 compare in the rankings?
Player hours over seven days put acceptance002 at #15,977, in the top 71% of the ranked set.
What population does acceptance002 carry?
Offline now for acceptance002, with the last sample 22 days 18 hours ago.
Server facts
What Rust version does acceptance002 run?
The build is Rust network protocol 2634 and build 166652 on Linux, run by acceptance002. Joining needs the same protocol on your game; Steam handles the update.
How reliable is acceptance002, and is it up?
acceptance002 is offline at this refresh; the last response came 22 days 18 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 4 October 2026.
Which location does acceptance002 run from?
No region is published by acceptance002. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. You can reach it at 45.83.145.30:28415.
Settings and map
Which settings and rules does acceptance002 run?
No gather rate appears in the name: acceptance002. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: gather, build, raid: the standard loop. Fighting and raiding between players are allowed. It is a community server, and the browser files it under Community. Its own label is vanilla: no changed rates, kits or rules: the game as Facepunch ships it. VAC is running: Valve's anti-cheat is on.
Which map has acceptance002 loaded?
A procedural map runs on acceptance002, generated by the game.
Wipes and dates
When does acceptance002 wipe, and how often?
The record for acceptance002 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 23 days 14 hours ago.
On acceptance002, what happens on wipe day?
Across recent wipes the busiest point averaged 0 players. The crowd on the latest wipe topped out 0 hours after it began.
Lists and tags
Where does acceptance002 appear among Rust Data lists and filters?
These Rust Data lists include acceptance002: Rust community servers, unfiltered and Vanilla Rust servers. These filters bring it up on the server list: Type: Vanilla, Community (not modded, not official) and No plugins at all; Server tag: Vanilla ^v; Group limit: 5 or more.
How should you read the server tags on acceptance002?
These tags are published by acceptance002 and read by the game's server browser: gmvanilla (Game mode): Survival in vanilla form; mp10 (Max players): The server lists 10 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): The region field is empty; ^v (Vanilla): No changed rates, kits or rules: the game as Facepunch ships it. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
How to join
What is the way into acceptance002?
In Rust, F1 opens the console: type client.connect 45.83.145.30:28415. Launch Rust on this page does the same by opening the game through Steam and connecting.