Working its way up from the back of the class: #15,222 on player hours.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
52/ 100
D
Moving up: up 700 places this week.
A term to build on.
Strongest in momentum (D); standing is the one to work on (F).
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
Average fpsLowest fpsWipe
Most entitiesWipe
Most memory, MBWipe
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 best
RankRank in region
Top 70% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····W··
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak0players, 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
Peak
Crowd
Lasted
Players before
Fri 9 Oct, 09:40 UTC19d ago
0
–
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Which region is Pykeron | Vanilla+ x1 | 3000 | RO based in?
No region is published for Pykeron | Vanilla+ x1 | 3000 | RO. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. You can connect at 90.95.132.38:28015.
Is Pykeron | Vanilla+ x1 | 3000 | RO up, and how steady is its uptime?
You cannot join now: Pykeron | Vanilla+ x1 | 3000 | RO is offline, last seen 14 days 17 hours ago. It was up 0 of 168 hours over the last 7 full days, which is 0% of the time. It was first seen by Rust Server Score on 18 September 2026.
What Rust version is Pykeron | Vanilla+ x1 | 3000 | RO on?
The server Pykeron | Vanilla+ x1 | 3000 | RO is on Rust network protocol 2634 and build 167781 under Linux. To join, your game must use the same protocol; Steam handles the update.
Wipe schedule
When does Pykeron | Vanilla+ x1 | 3000 | RO wipe, and how often?
The record holds too few of Pykeron | Vanilla+ x1 | 3000 | RO's wipes to tell its rhythm. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. It has been running its current world for 19 days 19 hours.
What happens on Pykeron | Vanilla+ x1 | 3000 | RO when wipe day arrives?
The average peak on its recent wipes was 0 players. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does Pykeron | Vanilla+ x1 | 3000 | RO place in the wider field of Rust servers?
Over the last seven days, Pykeron | Vanilla+ x1 | 3000 | RO has #15,222 for player hours, in the top 70% of all ranked servers.
What does the population on Pykeron | Vanilla+ x1 | 3000 | RO look like?
Pykeron | Vanilla+ x1 | 3000 | RO is offline at the moment; the last time it was seen was 14 days 17 hours ago.
Lists and filters
What is meant by the tags on Pykeron | Vanilla+ x1 | 3000 | RO?
You'll see Pykeron | Vanilla+ x1 | 3000 | RO tagged with gmrust (Game mode): Survival in the standard Rust style; mp20 (Max players): 20 slots are available; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): This runs on build 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded; ^y (Carbon): The plugin framework in use is Carbon in the browser, which picks them up from the server. Its tags also carry today's player number, the queue length and the world's creation time, which you'll find at the top of this page.
Where does Pykeron | Vanilla+ x1 | 3000 | RO appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Pykeron | Vanilla+ x1 | 3000 | RO: Modded Rust servers, graded. You can find it under these server-list filters: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Gather rate: 1x.
Rules and settings
Which rules does Pykeron | Vanilla+ x1 | 3000 | RO enforce, and what are its settings?
Pykeron | Vanilla+ x1 | 3000 | RO sets gather at 1x, as its name suggests. The group limit stays at the game's default of 8 players. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. Plugins or settings change the game here, and the server browser lists it under Modded. The plugin count runs to Carbon. You are covered by VAC, Valve's anti-cheat.
Can you tell me which map Pykeron | Vanilla+ x1 | 3000 | RO uses?
Pykeron | Vanilla+ x1 | 3000 | RO runs a game-generated procedural map at size 3,000, seed 1. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How should you connect to Pykeron | Vanilla+ x1 | 3000 | RO?
To connect, start Rust, press F1, and type client.connect 90.95.132.38:28015. Or click Launch Rust here, which launches Rust through Steam and joins you. The website for this server is https://pykeron.com/.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2634,gmrust,cs167781,ts8,^z,^y
Game
gmrust
Game modeSurvival in the standard Rust style.
mp20
Max players20 slots are available.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThis runs on build 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
^y
CarbonThe plugin framework in use is Carbon.
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.
A term to build on. Strongest in momentum (D); standing is the one to work on (F).