Offline 212.247.125.89:27015 checked 16d ago
Pelican Test
Connect
srv = rust.server("212.247.125.89:27017")
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 66% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 6d 9h. # The force wipe
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · no wipe seen yet. | |||||
# 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
- 212.247.125.89:27015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- monthly
- last wipe
- 14 Oct 2026, 00:18 UTC
- hostname
- –
- first seen
- 14 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 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 97 on average | 36/700 |
| 1 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 95 on average | 107/700 |
| 2 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 85 on average | 14/1000 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 | EU · groups of 16+ · monthly · 80 on average | 44/1000 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 | EU · groups of 16+ · monthly · 77 on average | 90/1000 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 | EU · groups of 16+ · monthly · 73 on average | 236/1000 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does Pelican Test rank?
Rank #14,234 on seven-day player hours for Pelican Test, within the top 66% of all ranked servers.
What population does Pelican Test carry?
Offline now for Pelican Test, with the last sample 16 days 8 hours ago.
About the server
Which Rust version is Pelican Test on?
The build is Rust network protocol 2634 and build 167781 on Linux, run by Pelican Test. Steam updates your game for you, but the protocol must match to join.
Is Pelican Test up, and what does its uptime show?
Pelican Test is offline at this refresh; the last response came 16 days 8 hours ago. Uptime of 0% across the last 7 full days: 0 hours of 168. The first row Rust Data holds for it is dated 14 October 2026.
Where does Pelican Test sit?
For Pelican Test, no region is published. Rust Data does not look up where the machine stands; it shows where a server says it is. 212.247.125.89:27015 is its address.
Settings and map
What rules and settings are recorded for Pelican Test?
You will not find a gather rate in the string Pelican Test. The group limit sits at the default of 8 players. Game mode survival, with this note: the usual game, with gathering, building and raiding. Fighting and raiding between players are allowed. Browser listing: Modded. Plugins or settings modify the game. Plugins installed: Carbon. Vanilla, by its own description: facepunch's stock game, with rates, kits and rules untouched. VAC is running: Valve's anti-cheat is on.
What is the map on Pelican Test?
The game generates its map: procedural, on Pelican Test.
Wipe schedule
When does Pelican Test wipe, and on what schedule?
The next wipe for Pelican Test is an estimate, drawn from the force wipe. On Thursday 5 November at 19:00 UTC the force wipe comes; that is the next wipe, and every Rust server takes it. This world was created 16 days 8 hours ago. Its tags carry a monthly wipe schedule.
Tags and filters
Which lists on Rust Data hold Pelican Test, and which filters?
On Rust Data, Pelican Test appears in these lists: Modded Rust servers. Under these filters on the server list, it is listed: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the server tags on Pelican Test?
The game's server browser reads these tags from Pelican Test: gmvanilla (Game mode): The mode is vanilla survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs167781 (Build): The server runs build 167781; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^m (Monthly): Wipes follow the monthly force wipe from Facepunch; ^v (Vanilla): Facepunch's stock game, with rates, kits and rules untouched; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Runs on Carbon for plugins. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
How to join
How can I connect to Pelican Test?
The manual route: launch Rust, F1, then client.connect 212.247.125.89:27015. The shortcut is Launch Rust on this page, which opens the game through Steam and connects you.