Rust Server TrendsSeismic network · station log
Recording Stations11,615 Players40,974 Active2,914 Wipes · 3 h146 48 h

Station XX-14234 · no signal

Pelican Test

Offline 212.247.125.89:27015 checked 16d ago

monthly wipes vanillamoddedcarbon
Connect
Players now
1/ 50
2% full
Motion · 24 h
M –
too few hourly readings
7-day average
0
peak –
Rank
#14,234
top 66%
Last wipe
16d ago
monthly schedule
Next wipe
6d 12h
Thu 5 Nov, 19:00 UTC FW
Seismic record · station XX-14234 · CH Z

The last 48 hours, hour by hour

hourly average players · UTC
No signal: too few hourly readings to draw a record yet.
Now
1of 50 slots
Motion · 24 h
M –not enough readings
Channel 1 · calibrated

Players

No hourly history yet.

Hourly average and peak, UTC.

Channel 2 · instrument health

Server performance

This server has not answered a direct query in the last 48 hours.

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.

Channel 3 · rank movement

Rank

daily · 1 is best
RankRank in region
15k10k15k20k14 Oct15 Oct16 Oct18 Oct19 Oct20 Oct

Top 66% of all ranked servers. Ranked on player hours over the last seven days.

Expected events

Wipe schedule

Next wipe Thursday 5 November, 19:00 UTC, in 6d 12h. The force wipe

Event catalogue

Wipes

newest first
WipedMPeakFirst 48 hCrowdLastedPlayers before
No wipe seen yet.

Peak: the most players in the first 48 hours. M: the magnitude of the wipe, log10 of the rise from the players before it to that peak. First 48 h: its players hour by hour from the wipe. 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.

Nearby stations

Similar servers

the same kind of game, then region, group limit, rate and wipes
404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 EU · groups of 16+ · monthly · 97 on average
11/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 EU · groups of 16+ · monthly · 94 on average
47/ 700
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 EU · groups of 16+ · monthly · 85 on average
4/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|МОСКОВСКИЙ 26.10 EU · groups of 16+ · monthly · 80 on average
21/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЙСКИЙ 28.10 EU · groups of 16+ · monthly · 77 on average
51/ 1000
404 RUST 2Х|ДЛЯ НОВИЧКОВ|РОССИЯ 29.10 EU · groups of 16+ · monthly · 74 on average
85/ 1000
Readings, in words

Quick answers

from the figures on this page

Server rules

Which map is running on Pelican Test?

Pelican Test uses a procedural map, which the game generates.

Which settings and rules apply on Pelican Test?

The name of Pelican Test gives no gather rate. Groups hold up to 8 players, which is the default for the game. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. The server browser lists it under Modded, where plugins or settings change the game. The plugins run on Carbon. It describes itself as vanilla, which means rates, kits and rules are as Facepunch ships them. VAC, Valve's anti-cheat, is switched on.

Player counts

How many players are recorded on Pelican Test right now?

Pelican Test is not responding at this moment and is offline, last seen 16 days 5 hours ago.

How does Pelican Test rank against other Rust servers?

The last seven days of player hours place Pelican Test at #14,234, in the top 66% of all ranked servers.

Server details

How reliably does Pelican Test stay online?

No contact with Pelican Test right now, and the last recorded contact was 16 days 5 hours ago. It was up 0% of the time across the last 7 full days: 0 of 168 hours. On 14 October 2026 it was recorded for the first time by Rust Server Trends.

Which region does Pelican Test run from?

A region is not published by Pelican Test. Where a server says it is, that is what Rust Server Trends shows, without looking up where the machine stands. 212.247.125.89:27015 is the address it uses.

Which Rust version is Pelican Test running?

On Linux, Pelican Test runs Rust network protocol 2634 and build 167781. Steam updates your game for you, but it has to be on the same protocol as the server to join.

Wipe pattern

How often does Pelican Test wipe, and on which days?

From the force wipe the next wipe of Pelican Test is estimated. When every Rust server wipes, at the force wipe on Thursday 5 November at 19:00 UTC, it takes its next wipe. 16 days 6 hours is how long the current world has been running. Its tags state a monthly wipe schedule.

Server tags

What do the server tags on Pelican Test mean?

Tags published by Pelican Test and read by the game's server browser include gmvanilla (Game mode): You'll find vanilla survival here; mp50 (Max players): 50 slots are available; ts8 (Group limit): This uses the game default of 8 per team; v2634 (Protocol): Game protocol 2634: to join, your game must match this version; cs167781 (Build): Game build: 167781; ptrak (Networking): RakNet is the standard network layer for the game, and it's used here; $r? (Region code): The server has no region code; ^m (Monthly): Once a month it wipes, with the force wipe from Facepunch; ^v (Vanilla): Rates, kits and rules are as Facepunch ships them; ^z (Modded): The game is changed by plugins or settings, placing it under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. The tags also carry its current players, its queue and when its world was made, shown at the top of this page.

On which Rust Server Trends lists does Pelican Test appear?

These Rust Server Trends lists include Pelican Test: Modded Rust servers, tracked live. On the server list, the filters it matches are: Type: Vanilla and Modded; Server tag: Monthly ^m, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Monthly.

Connecting

What steps get you onto Pelican Test?

Enter client.connect 212.247.125.89:27015 in the Rust console (F1), or take the Launch Rust button on this page, which opens Rust through Steam and connects you.

Instrument codes

Server tags

what each one means

Published as mp50,ptrak,$r?,v2634,^z,^y,^m,^v,gmvanilla,cs167781,ts8

Game

gmvanilla
Game mode You'll find vanilla survival here.
mp50
Max players 50 slots are available.
ts8
Group limit This uses the game default of 8 per team.
v2634
Protocol Game protocol 2634: to join, your game must match this version.
cs167781
Build Game build: 167781.
ptrak
Networking RakNet is the standard network layer for the game, and it's used here.
$r?
Region code The server has no region code.

Wipe schedule

^m
Monthly Once a month it wipes, with the force wipe from Facepunch.

Difficulty

^v
Vanilla Rates, kits and rules are as Facepunch ships them.

Mods and access

^z
Modded The game is changed by plugins or settings, placing it under Modded.
^y
Carbon A plugin framework, Carbon, runs here.

Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.

Magnitude scale. M = log10 of the absolute the change in players over 24 hours: M1.0 is 10 players, M2.0 is 100, M3.0 is 1,000. Classes: micro under 1, minor 1–2, light 2–3, moderate 3–4, strong 4 and over. ▲ rising, ▼ falling.