Offline 193.81.122.89:28015 checked 19d ago
greenpool.dev
Connect
srv = rust.server("193.81.122.89: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 72% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · force wipes only
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 7d 4h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 7d 4h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 35d 4h | Thu 3 Dec, 19:00 UTC | FW force wipe |
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Thu 1 Oct, 18:13 UTC FW27d ago | 1 | NaN | running | 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
- 193.81.122.89:28015
- region
- –
- max players
- 2
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 1 Oct 2026, 18:13 UTC
- hostname
- –
- first seen
- 25 Sep 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 · 149 on average | 172/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 130/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 119 on average | 133/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 94 on average | 78/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 48/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 85 on average | 242/700 |
Quick answers
From the figures on this page.
Population
How does greenpool.dev compare in the rankings?
Over the last seven days greenpool.dev sits at #15,812 on player hours, in the top 72% of ranked servers.
How full does greenpool.dev run?
Offline now for greenpool.dev, with the last sample 19 days 18 hours ago.
About the server
What is the Rust version on greenpool.dev?
Rust network protocol 2634 and build 166652 on Linux is what greenpool.dev runs. Joining needs the same protocol on your game; Steam handles the update.
How reliable is greenpool.dev, and is it up?
greenpool.dev is offline at this refresh; the last response came 19 days 18 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. Rust Data logged it first on 25 September 2026.
Which location does greenpool.dev run from?
There is no region published for greenpool.dev. Rust Data does not look up where the machine stands; it shows where a server says it is. 193.81.122.89:28015 is its address.
Settings and map
What rules and settings are recorded for greenpool.dev?
You will not find a gather rate in the string greenpool.dev. No custom cap; the default of 8 players per group stands. survival is the game mode here, and the base game, where you gather, build and raid. Combat and raiding between players: both allowed. Browser listing: Modded. Plugins or settings modify the game. The plugin count is Oxide. Anti-cheat status: VAC on.
Which map has greenpool.dev loaded?
A procedural map runs on greenpool.dev, generated by the game.
Wipe data
On what schedule does greenpool.dev wipe?
A single wipe each month, the force wipe, is all greenpool.dev does. Its next wipe falls on Thursday 5 November at 19:00 UTC with the force wipe that hits all Rust servers. A new world was started 27 days 20 hours ago, and that is the one in play.
What is wipe day on greenpool.dev like?
Across recent wipes the busiest point averaged 1 players. The crowd on the latest wipe topped out 2 hours after it began.
Tags and filters
Which lists on Rust Data hold greenpool.dev, and which filters?
On Rust Data, greenpool.dev appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
How should you read the server tags on greenpool.dev?
Read by the game's server browser, the tags greenpool.dev publishes are: gmrust (Game mode): Survival play, standard Rust; mp2 (Max players): Slot count: 2; ts8 (Group limit): Unchanged from default, teams hold up to 8; v2634 (Protocol): To join, your game must run protocol 2634; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): No region code is set; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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 to join greenpool.dev?
In Rust, F1 opens the console: type client.connect 193.81.122.89:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.