On the class lists: F (34), with population over 48 hours and no performance mark.
Players now0/ 1000% full
7-day average0peak 1
Rank#9,815top 44% · #2252 in EU
Last wipe12d agoweekly schedule
Next wipe1d 15hThu 29 Oct, 14:12 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 100 on average. Plenty of space to grow.
Standingrank on player hours
56/ 100
C−
Working its way up from the back of the class: #9,815 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
50/ 100
D
Slows down under load at times: 30 server fps on average.
Wipeskeeping the crowd after a wipe
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
18/ 100
F
Lost ground: down 6,253 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in uptime (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 44% of all ranked servers, top 77% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
3 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
·······
···F···
·······
···W···
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
from its schedule tag
Next wipe Thursday 29 October, 14:12 UTC, in 1d 15h.
Its weekly schedule tag · low confidence
usual gap13.9 daysbetween real wipes
on rhythm100%of its recent wipes
wipe-day peak1players, last three wipes
crowd held0%else halves by day 4
Coming wipes
1d 15hThu 29 Oct, 14:12 UTC
8d 20hThu 5 Nov, 19:00 UTCFW
15d 15hThu 12 Nov, 14:12 UTC
22d 15hThu 19 Nov, 14:12 UTC
29d 15hThu 26 Nov, 14:12 UTC
36d 20hThu 3 Dec, 19:00 UTCFW
43d 15hThu 10 Dec, 14:12 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctThu 17 Sep
Players each hour, from the hour of the wipe. The latest peaked at 3, 4 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 14:12 UTC12d ago
3
–
running
2
Thu 1 Oct, 18:10 UTCFW26d ago
1
halved by day 4
13.8 days
1
Thu 17 Sep, 18:11 UTC40d ago
0
–
14 days
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
Which region is [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full based in?
The EU tag on [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full puts it in Europe. Rust Server Score takes the server's word for its location and does not trace the hardware. You can connect at 64.40.9.110:28015.
How reliable is [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full, and is it up?
You can join now: [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full is online. About 16 hours ago, it restarted, based on the uptime it reports. For the last 7 full days, it was up 168 of 168 hours, or 100% of the time. On 13 September 2026, Rust Server Score saw it for the first time.
Is [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full smooth to play on?
The average over the last 48 hours was 30 server fps, and it never went below 29. At its peak, it held 121,429 entities, including buildings, deployables and all else in the world. Memory use reached up to 4,724 MB. Players feel lag when fps drops and entities pile up.
What Rust version is [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full on?
The server [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full is on Rust network protocol 2635 and build 168909 under Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full wipe its map?
The prediction follows its tag, because too few of [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full's wipes are on record to confirm the schedule. Expect the next wipe on Thursday 29 October at 14:12 UTC. The world it runs now was created 12 days 8 hours. Wipes are scheduled weekly, according to its tags.
What should you expect from wipe day on [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full?
The average peak on its recent wipes was 1 players. The crowd on the latest wipe was largest 4 hours after it began. The crowd stayed above half that peak, right through to the next wipe, in 0% of its recent wipes. The crowd dropped below half by day 4 in the wipes where it did not hold.
Population
Where does [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full sit among Rust servers?
Over the last seven days, [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full has #9,815 for player hours, in the top 44% of all ranked servers and #2,252 in Europe.
Is [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full a busy server?
[EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full is showing 0 players right now, with 100 slots in total. The seven-day average is 0 players, with a peak of 1.
Tags
How should you read the tags on [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full?
The game's browser takes its cue from the tags [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full has set: gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): Its slot count is 100; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): This runs on build 168909; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): It wipes weekly; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^z (Modded): The game is changed by plugins or settings; you will find it under Modded; ^y (Carbon): The plugin framework in use is Carbon; EU (Europe): In the server browser it appears under Europe. 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 [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full?
These Rust Server Score lists count [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full among them: European Rust servers, graded and Modded Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: 5 or more; Wipe schedule: Weekly; Last wipe: In the last 2 weeks.
Rules and settings
What settings and rules apply on [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full?
Nothing in the name of [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full states a gather rate. The default of 8 players applies as the group cap. You get survival here, gather, build and raid, as in the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Carbon. By its own description it is vanilla: nothing is altered here: rates, kits and rules are as Facepunch ships them. The server runs Valve's anti-cheat, VAC.
[EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full runs which map?
[EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full runs a game-generated procedural map at size 4,500, seed 1668698039. A matching size and seed produce the same map, viewable on RustMaps from this page.
Connecting
How should you connect to [EN/GER] Get Rusted |Solo-Trio|Weekly noBP|Biweekly Full?
Enter client.connect 64.40.9.110:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. The website for this server is https://rust-vip-shop.tebex.io/.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2635,^z,^y,^w,^v,EU,gmrust,cs168909,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max playersIts slot count is 100.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThis runs on build 168909.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyIt wipes weekly.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^z
ModdedThe game is changed by plugins or settings; you will find it under Modded.
^y
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeIn the server browser it appears under Europe.
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 uptime (A+); population is the one to work on (F).