Offline 152.233.12.65:28215 checked 2d ago
Pingplayers reference server
Connect
srv = rust.server("152.233.12.65:28217")
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 69% 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 | Tue 27 Oct, 02:43 UTC2d 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
- 152.233.12.65:28215
- region
- –
- max players
- 500
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 27 Oct 2026, 02:43 UTC
- hostname
- –
- first seen
- 27 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 | ShockRust | Blue | NoLimit | no group limit · 151 on average | 50/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 120/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 117 on average | 69/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 20/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 3/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 7/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Pingplayers reference server rank?
Player hours over seven days put Pingplayers reference server at #15,341, in the top 69% of the ranked set.
What population does Pingplayers reference server carry?
Pingplayers reference server returns no live count at this refresh, having last been seen 2 days 3 hours ago. Over the last seven days it averaged 0 players.
Server facts
Which Rust version is Pingplayers reference server on?
Rust network protocol 2635 and build 168909 on Linux is what Pingplayers reference server runs. Steam updates your game for you, but the protocol must match to join.
How reliable is Pingplayers reference server, and is it up?
Offline now for Pingplayers reference server, last seen 2 days 3 hours ago. Uptime of 0% across the last 1 full day: 0 hours of 24. Its earliest recorded date in Rust Data is 27 October 2026.
In which location is Pingplayers reference server hosted?
There is no region published for Pingplayers reference server. Where a server says it is, that is what Rust Data shows; the machine's actual location is not looked up. 152.233.12.65:28215 is its address.
Map and rules
Which rules apply on Pingplayers reference server, and what settings?
The name Pingplayers reference server carries no gather rate. Eight players per group: that is the game's default, and it applies here. Game mode survival, with this note: the usual game, with gathering, building and raiding. Raids and player combat are enabled. Browser listing: Modded. Plugins or settings modify the game. Carbon plugins run on it. VAC is running: Valve's anti-cheat is on.
Which map has Pingplayers reference server loaded?
Pingplayers reference server runs a procedural map, which the game generates.
Wipes and dates
On what schedule does Pingplayers reference server wipe?
Too few wipes are on record for Pingplayers reference server to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. A new world was started 2 days 3 hours ago, and that is the one in play.
On Pingplayers reference server, 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.
Tags and filters
Which lists on Rust Data hold Pingplayers reference server, and which filters?
The Rust Data lists that Pingplayers reference server fits are: Modded Rust servers. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last 3 days.
How should you read the server tags on Pingplayers reference server?
These tags are published by Pingplayers reference server and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp500 (Max players): Slot count: 500; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2635 (Protocol): To join, your game must run protocol 2635; cs168909 (Build): The server runs build 168909; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): Region code: not set; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. 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 Pingplayers reference server?
In Rust, F1 opens the console: type client.connect 152.233.12.65:28215. Launch Rust on this page does the same by opening the game through Steam and connecting.