On the class lists: F (44), with population over 48 hours and no performance mark.
Players now0/ 30% full
7-day average0peak –
Rank#15,409top 69%
Last wipe15d agono schedule published
Next wipe–too few wipes seen yet
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 3 on average. Plenty of space to grow.
Standingrank on player hours
31/ 100
F
Working its way up from the back of the class: #15,409 on player hours.
Uptimehours on the list, last 48
98/ 100
A+
Excellent attendance: on the list 47 of the last 48 hours.
Performanceserver fps, last 48 hours
100/ 100
A+
Runs smoothly: 189 server fps on average.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
49/ 100
D
Slipped a little: down 179 places this week. Nothing a good wipe can't fix.
A fair term, with more to come.
Strongest in performance (A+); population 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
Every five minutes, from the Steam server list.
AveragePeak
Hourly average and peak, UTC.
AveragePeakWipe
Daily average and peak, UTC.
Server performance
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 17 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 69% 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
Mon 12 Oct, 13:31 UTC15d ago
0
–
running
0
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
gdpy leaves the region unpublished. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 220.158.30.44:28015 is the address to use.
How reliable is gdpy, and is it up?
You can join now: gdpy is online. According to its reported uptime, the last restart was about 10 days 4 hours ago. It was up 144 of 168 hours over the last 7 full days, which is 86% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Does gdpy perform well?
The average over the last 48 hours was 189 server fps, and it never went below 126. Up to 48,393 entities were in the world, covering buildings, deployables and the rest. Memory use reached up to 2,749 MB. Players feel lag when fps drops and entities pile up.
On what Rust version does gdpy sit?
Rust network protocol 2634 and build 167781 on Linux is what gdpy runs. Steam updates your game for you, but you need the same protocol to join.
Resets
When does gdpy wipe, and how often?
There are too few wipes on record for gdpy to show a rhythm. On Thursday 5 November at 19:00 UTC the monthly force wipe resets every Rust server. The world it runs now was created 15 days 11 hours.
What happens on gdpy when wipe day arrives?
The average peak on its recent wipes was 0 players. The crowd on the latest wipe was largest 0 hours after it began.
Player numbers
Where does gdpy place in the wider field of Rust servers?
Over the last seven days, gdpy has #15,409 for player hours, in the top 69% of all ranked servers.
What does the population on gdpy look like?
With 3 slots available, gdpy currently has 0 players. A seven-day average of 0 players applies here.
Tags and filters
How should you read the tags on gdpy?
You'll see gdpy tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp3 (Max players): 3 slots are available; ts8 (Group limit): A team can hold 8 at most, which is the game default; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): The game build is 167781; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): A region code is not set here in the browser, which picks them up from the server. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which Rust Server Score filters and lists feature gdpy?
Rust Server Score lists that include gdpy: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
Which rules does gdpy enforce, and what are its settings?
You will find no gather rate in the name of gdpy. With no change from the game default, groups take up to 8 players. survival is the mode here, gather, build and raid, as in the standard game. You can raid other players and fight them. Under Community in the server browser you will find this community server. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map gdpy uses?
The game generates the procedural map on gdpy at size 3,000 with seed 50000. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto gdpy?
To connect, start Rust, press F1, and type client.connect 220.158.30.44:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2634,gmrust,cs167781,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp3
Max players3 slots are available.
ts8
Group limitA team can hold 8 at most, which is the game default.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildThe game build is 167781.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeA region code is not set 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.
A fair term, with more to come. Strongest in performance (A+); population is the one to work on (F).