On the class lists: D (48), with population over 48 hours and no performance mark.
Players now0/ 2000% full
7-day average0peak 4
Rank#5,310top 24% · #1757 in EU
Last wipe13d agobiweekly schedule
Next wipe16hThu 29 Oct, 14:07 UTC
Subjects
Subject
Mark
Grade
Teacher's comment
Populationplayers against slots, 7-day average
0/ 100
F
A quiet classroom so far: 0 of 200 on average. Plenty of space to grow.
Standingrank on player hours
76/ 100
B
Holds a respectable place: #5,310 on player hours.
Uptimehours on the list, last 48
94/ 100
A
Good attendance: on the list 45 of the last 48 hours.
Performanceserver fps, last 48 hours
75/ 100
B
Mostly smooth: 45 server fps on average.
Wipeskeeping the crowd after a wipe
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
39/ 100
F
Slipped a little: down 1,215 places this week. Nothing a good wipe can't fix.
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 24% of all ranked servers, top 60% in EU, and #355 of the trio servers (top 57%). Ranked on player hours over the last seven days.
Attendance: the wipe record
4 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
···W···
··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:07 UTC, in 16h.
Its biweekly schedule tag · low confidence
usual gap8 daysbetween real wipes
on rhythm33%of its recent wipes
wipe-day peak3players, last three wipes
crowd held33%else halves by day 4.5
Coming wipes
16hThu 29 Oct, 14:07 UTC
7d 20hThu 5 Nov, 19:00 UTCFW
14d 16hThu 12 Nov, 14:07 UTC
28d 16hThu 26 Nov, 14:07 UTC
35d 20hThu 3 Dec, 19:00 UTCFW
42d 16hThu 10 Dec, 14:07 UTC
The first 48 hours of its last wipes
Thu 15 OctThu 1 OctWed 23 Sep
Players each hour, from the hour of the wipe. The latest peaked at 1, 6 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Thu 15 Oct, 14:07 UTC13d ago
1
–
running
0
Thu 1 Oct, 17:55 UTCFW27d ago
4
halved by day 8
13.8 days
0
Wed 23 Sep, 17:43 UTC35d ago
4
halved by day 1
8 days
3
Thu 17 Sep, 14:08 UTC41d ago
3
✓ held half
6.1 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
In what location does [EU] Grimlands.eu - Trio | Biweekly sit?
The EU tag on [EU] Grimlands.eu - Trio | Biweekly puts it in Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 158.174.102.177:28015.
How dependable is [EU] Grimlands.eu - Trio | Biweekly, and is it online at the moment?
The server is up: [EU] Grimlands.eu - Trio | Biweekly is online now. According to its reported uptime, the last restart was about 17 hours ago. It was up 168 of 168 hours over the last 7 full days, which is 100% of the time. The first sighting by Rust Server Score was on 13 September 2026.
How well does [EU] Grimlands.eu - Trio | Biweekly run?
It averaged 45 server fps over the last 48 hours, with a low of 42. At its peak, it held 105,877 entities, including buildings, deployables and all else in the world. At its highest, it used 3,594 MB of memory. When fps is low and entities climb, that is lag to players.
On what Rust version does [EU] Grimlands.eu - Trio | Biweekly sit?
Rust network protocol 2635 and build 168909 on Linux is what [EU] Grimlands.eu - Trio | Biweekly runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [EU] Grimlands.eu - Trio | Biweekly wipe, and how often?
The prediction follows its tag, because too few of [EU] Grimlands.eu - Trio | Biweekly's wipes are on record to confirm the schedule. Expect the next wipe on Thursday 29 October at 14:07 UTC. 13 days 7 hours have passed since this world was made. Its tags give a wipe schedule of every two weeks.
What should you expect from wipe day on [EU] Grimlands.eu - Trio | Biweekly?
The average peak on its recent wipes was 3 players. Peak numbers came 6 hours into the latest wipe. The crowd stayed above half that peak, right through to the next wipe, in 33% of its recent wipes. Day 4.5 is when it sank below half in the wipes that did not hold.
Population
Where does [EU] Grimlands.eu - Trio | Biweekly place in the wider field of Rust servers?
In Europe, [EU] Grimlands.eu - Trio | Biweekly is #1,757, and overall it is #5,310 on player hours over the last seven days, in the top 24% of all ranked servers. It comes #355 among servers in the trio group.
How many players does [EU] Grimlands.eu - Trio | Biweekly usually have?
With 200 slots available, [EU] Grimlands.eu - Trio | Biweekly currently has 0 players. Averaging 0 players over seven days, it peaked at 4. The highest average in the last 48 hours came at 07:00 UTC, with 1 players.
Tags
What is meant by the tags on [EU] Grimlands.eu - Trio | Biweekly?
You'll see [EU] Grimlands.eu - Trio | Biweekly tagged with gmrust (Game mode): Survival in the standard Rust style; mp200 (Max players): 200 slots are available; ts3 (Group limit): No team may go above 3; v2635 (Protocol): The game protocol is 2635, so your game must match that version to join; cs168909 (Build): The game build is 168909; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): The server wipes on a two-week cycle; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^o (Oxide): Plugin framework: Oxide (uMod); EU (Europe): You will find it under Europe in the browser 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.
Who operates [EU] Grimlands.eu - Trio | Biweekly?
A grimlands.eu hostname is published by [EU] Grimlands.eu - Trio | Biweekly and by 4 other tracked servers, which suggests one operator.
Which lists and filters on Rust Server Score show [EU] Grimlands.eu - Trio | Biweekly?
Rust Server Score lists that include [EU] Grimlands.eu - Trio | Biweekly: European Rust servers, graded, Best community servers, graded, Rust servers with a trio group limit and Vanilla Rust servers, graded. You can find it under these server-list filters: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: Trio; Wipe schedule: Every two weeks; Last wipe: In the last 2 weeks.
Rules and settings
Which rules does [EU] Grimlands.eu - Trio | Biweekly enforce, and what are its settings?
Nothing in the name of [EU] Grimlands.eu - Trio | Biweekly states a gather rate. The cap on group size is 3 players (trio). You get survival here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. You will see it in the Community section of the server browser, since it is a community server. Plugins on it number Oxide. The vanilla label is its own: you get the unmodified game: no rate changes, no kits, no rule changes. VAC, Valve's anti-cheat, is enabled.
[EU] Grimlands.eu - Trio | Biweekly runs which map?
A procedural map of size 4,250 and seed 1599161133, generated by the game, is what [EU] Grimlands.eu - Trio | Biweekly runs. You can look at the map on RustMaps from this page, since identical size and seed produce an identical map.
Getting in
How do you get onto [EU] Grimlands.eu - Trio | Biweekly?
Enter client.connect 158.174.102.177: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://grimlands.eu.
Server tags
what each one means
Published asmp200,ptrak,$r?,v2635,^b,^v,EU,gmrust,cs168909,ts3,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp200
Max players200 slots are available.
ts3
Group limitNo team may go above 3.
v2635
ProtocolThe game protocol is 2635, so your game must match that version to join.
cs168909
BuildThe game build is 168909.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyThe server wipes on a two-week cycle.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^o
OxidePlugin framework: Oxide (uMod).
Region
EU
EuropeYou will find it under Europe in the browser.
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).