Station XX-15222 · no signal
Pykeron | Vanilla+ x1 | 3000 | RO
Offline 90.95.132.38:28015 checked 38d ago
- Players now
- 0/ 20
- 0% full
- Motion · 24 h
- M –
- too few hourly readings
- 7-day average
- 0
- peak –
- Rank
- #15,222
- top 70%
- Last wipe
- 43d ago
- no schedule published
- Next wipe
- –
- too few wipes seen yet
The last 48 hours, hour by hour
hourly average players · UTC- Now
- 0of 20 slots
- Motion · 24 h
- M –not enough readings
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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, measured since 18 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 70% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
- wipe-day peak
- 0players, last three wipes
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| Wiped | M | Peak | First 48 h | Crowd | Lasted | Players before |
|---|---|---|---|---|---|---|
| Thu 5 Nov, 19:00 UTC FW15d ago | – | – | – | – | running | – |
| Fri 9 Oct, 09:40 UTC43d ago | M0.0▼falling | 0 | – | – | 1 | |
| Thu 1 Oct, 18:00 UTC FW50d ago | – | – | – | – | – | – |
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.
Similar servers
the same kind of game, then region, group limit, rate and wipesQuick answers
from the figures on this pageRules and settings
Which map is running on Pykeron | Vanilla+ x1 | 3000 | RO?
Generated by the game, the map on Pykeron | Vanilla+ x1 | 3000 | RO is procedural, size 3,000 with seed 1. From this page you can look at it on RustMaps, since the same size and seed give the same map.
Which settings and rules apply on Pykeron | Vanilla+ x1 | 3000 | RO?
1x gather is what Pykeron | Vanilla+ x1 | 3000 | RO runs, judging by its name. The group limit is 8 players, the game's default. survival is the game mode, the usual game of gathering, building and raiding. Fighting and raiding between players are both allowed. Listed as Modded in the server browser, it changes the game through plugins or settings. Its plugins are run through Carbon. VAC, Valve's anti-cheat, is switched on.
Player counts
How many players are recorded on Pykeron | Vanilla+ x1 | 3000 | RO right now?
No players are recorded on Pykeron | Vanilla+ x1 | 3000 | RO at this moment; it is offline, and the last sighting was 38 days 1 hours ago.
How does Pykeron | Vanilla+ x1 | 3000 | RO rank against other Rust servers?
Over the last seven days, Pykeron | Vanilla+ x1 | 3000 | RO recorded enough player hours to reach #15,222 worldwide, placing it in the top 70% of all ranked servers.
Server details
How reliably does Pykeron | Vanilla+ x1 | 3000 | RO stay online?
No contact with Pykeron | Vanilla+ x1 | 3000 | RO right now, and the last recorded contact was 38 days 1 hours ago. Of the 168 hours in the last 7 full days, it was up for 0, or 0% of the time. 18 September 2026 is when Rust Server Trends first recorded it.
Which region does Pykeron | Vanilla+ x1 | 3000 | RO run from?
Nothing about a region comes from Pykeron | Vanilla+ x1 | 3000 | RO. The location shown by Rust Server Trends is the one a server claims, not a lookup of where the machine stands. 90.95.132.38:28015 is the address it uses.
What build of Rust does Pykeron | Vanilla+ x1 | 3000 | RO use?
On Linux, Pykeron | Vanilla+ x1 | 3000 | RO runs Rust network protocol 2634 and build 167781. You can only join when your game is on the same protocol, which Steam updates for you.
Wipe schedule
What does wipe day look like on Pykeron | Vanilla+ x1 | 3000 | RO?
On average, the busiest point of its recent wipes drew 0 players. The peak on the most recent wipe came 0 hours after the wipe.
How often does Pykeron | Vanilla+ x1 | 3000 | RO wipe, and on which days?
Too few wipes of Pykeron | Vanilla+ x1 | 3000 | RO are on record yet to show its rhythm. On Thursday 3 December at 19:00 UTC the monthly force wipe comes round, and every Rust server wipes with it. 43 days 3 hours is how long the current world has been running.
Lists and tags
What do the server tags on Pykeron | Vanilla+ x1 | 3000 | RO mean?
Tags published by Pykeron | Vanilla+ x1 | 3000 | RO and read by the game's server browser include gmrust (Game mode): Survival in standard Rust; mp20 (Max players): 20 slots are available; ts8 (Group limit): 8 per team is the default, and that's the limit here; 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): A region code has not been set; ^z (Modded): Plugins or settings alter the game, so it's listed under Modded; ^y (Carbon): A plugin framework, Carbon, runs here. Current players, queue length and world creation time sit in the tags as well, and appear at the top of this page.
On which Rust Server Trends lists does Pykeron | Vanilla+ x1 | 3000 | RO appear?
The Rust Server Trends lists that take in Pykeron | Vanilla+ x1 | 3000 | RO are: Modded Rust servers, tracked live. You will find it under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 1x.
How to join
What steps get you onto Pykeron | Vanilla+ x1 | 3000 | RO?
To join, enter client.connect 90.95.132.38:28015 in the console, opened with F1. Launch Rust and join on this page is the other option: it starts Rust through Steam and makes the connection for you.
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.