Working its way up from the back of the class: #15,797 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
51/ 100
D
Moving up: up 179 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 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 72% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
Where in the world is GER/ENG (Weekend Raid Times)?
You won't find a region tag on GER/ENG (Weekend Raid Times), but its name indicates Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. Find it at 203.16.163.183:28015.
Is GER/ENG (Weekend Raid Times) up, and how steady is its uptime?
At this moment, GER/ENG (Weekend Raid Times) is offline; the last time it was seen was 17 days 20 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 13 September 2026, Rust Server Score saw it for the first time.
On what Rust version does GER/ENG (Weekend Raid Times) sit?
Rust network protocol 2633 and build 165217 on Linux is what GER/ENG (Weekend Raid Times) runs. To join, your game must use the same protocol; Steam handles the update.
Resets
When does GER/ENG (Weekend Raid Times) wipe, and how often?
There are too few wipes on record for GER/ENG (Weekend Raid Times) to show a rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. 55 days 13 hours have passed since this world was made.
Player numbers
What position does GER/ENG (Weekend Raid Times) hold in the rankings?
Over the last seven days, GER/ENG (Weekend Raid Times) has #15,797 for player hours, in the top 72% of all ranked servers.
What does the population on GER/ENG (Weekend Raid Times) look like?
The last sighting of GER/ENG (Weekend Raid Times) was 17 days 20 hours ago, and it is offline right now.
Tags and filters
What do GER/ENG (Weekend Raid Times)'s tags stand for?
gmrust (Game mode): Survival in the standard Rust style; mp30 (Max players): The server holds 30 slots; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): To get in, your game needs to be on the same version: the protocol is 2633; cs165217 (Build): The game build is 165217; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): There is no region code on this server; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded are the tags GER/ENG (Weekend Raid Times) publishes, and the game's server browser reads them. The top of this page also shows its current players, any queue, and when the world was created, all from its tags.
Which lists and filters on Rust Server Score show GER/ENG (Weekend Raid Times)?
These Rust Server Score lists count GER/ENG (Weekend Raid Times) among them: European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Server rules
Which rules does GER/ENG (Weekend Raid Times) enforce, and what are its settings?
You will find no gather rate in the name of GER/ENG (Weekend Raid Times). The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. The server browser lists it as Modded: plugins or settings change how the game plays. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
GER/ENG (Weekend Raid Times) runs which map?
A procedural map of size 4,500 and seed 1145162262, generated by the game, is what GER/ENG (Weekend Raid Times) runs. A matching size and seed produce the same map, viewable on RustMaps from this page.
Getting in
How do you get onto GER/ENG (Weekend Raid Times)?
To connect, start Rust, press F1, and type client.connect 203.16.163.183:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2633,gmrust,cs165217,ts8,^o^z
Game
gmrust
Game modeSurvival in the standard Rust style.
mp30
Max playersThe server holds 30 slots.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolTo get in, your game needs to be on the same version: the protocol is 2633.
cs165217
BuildThe game build is 165217.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeThere is no region code on this server.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
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).