Working its way up from the back of the class: #16,643 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
0/ 100
F
Needs to keep more players after wipe day: 0% of wipes kept half their crowd.
Momentumrank now against a week ago
20/ 100
F
Lost ground: down 9,967 places this week. A strong wipe could turn it round.
A term to build on.
Strongest in standing (F); wipes are 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.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
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 71% of all ranked servers, top 87% in EU, and #516 of the trio servers (top 86%). Ranked on player hours over the last seven days.
Attendance: the wipe record
2 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
W···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 Friday 30 October, 09:29 UTC, in 2d 12h.
Its biweekly schedule tag · low confidence
usual gap3.8 daysbetween real wipes
wipe-day peak2players, last three wipes
crowd held0%else halves by day 1
Coming wipes
2d 12hFri 30 Oct, 09:29 UTC
8d 21hThu 5 Nov, 19:00 UTCFW
16d 12hFri 13 Nov, 09:29 UTC
30d 12hFri 27 Nov, 09:29 UTC
36d 21hThu 3 Dec, 19:00 UTCFW
44d 12hFri 11 Dec, 09:29 UTC
The first 48 hours of its last wipes
Fri 18 SepMon 14 Sep
Players each hour, from the hour of the wipe. The latest peaked at 3, 13 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Fri 18 Sep, 09:29 UTC39d ago
3
–
running
0
Mon 14 Sep, 14:32 UTC43d ago
2
halved by day 1
3.8 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
Where in the world is [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly?
You'll see [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly listed in Europe, tagged EU. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. Find it at 31.184.89.136:28015.
How reliable is [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly, and is it up?
At this moment, [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly is offline; the last time it was seen was 31 days 9 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly on?
You will find [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly on Rust network protocol 2633 and build 163794, hosted on Linux. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
When does [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly wipe, and how often?
The prediction follows its tag, because too few of [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly's wipes are on record to confirm the schedule. Friday 30 October at 09:29 UTC is the date set for its next wipe. It has been running its current world for 39 days 11 hours. Its tags say it wipes every two weeks.
What should you expect from wipe day on [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly?
Across its recent wipes, the busiest moments averaged 2 players. The crowd on the latest wipe was largest 13 hours after it began. Above half the peak until the next wipe: that was the pattern in 0% of its recent wipes. In the other wipes it slipped under half by day 1.
Player count
Where does [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly sit among Rust servers?
Over the last seven days, [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly has #16,643 for player hours, in the top 71% of all ranked servers and #2,571 in Europe. In the trio group, it ranks #516.
How many players does [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly usually have?
The last sighting of [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly was 31 days 9 hours ago, and it is offline right now.
Tags
What is meant by the tags on [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly?
The game's browser takes its cue from the tags [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly has set: gmrust (Game mode): Rust survival, played by the standard rules; mp30 (Max players): The server holds 30 slots; ts3 (Group limit): Teams cap out at 3; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): This runs on build 163794; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): Nothing is altered here: rates, kits and rules are as Facepunch ships them; ^y (Carbon): The plugin framework in use is Carbon; EU (Europe): The server browser lists it under Europe. 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.
Who is behind [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly?
A hvits.dev hostname is published by [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly, and 1 other server we track does the same, which points to one operator running them.
Which lists and filters on Rust Server Score show [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly?
These Rust Server Score lists count [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly among them: European Rust servers, graded, Best community servers, graded, Rust servers with a trio group limit and Vanilla Rust servers, graded. These filters bring it up on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Carbon ^y; Group limit: Trio; Wipe schedule: Every two weeks.
Server rules
Which rules does [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly enforce, and what are its settings?
Nothing in the name of [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly states a gather rate. The cap on group size is 3 players (trio). It runs survival, gather, build and raid, as in the standard game. Raiding and PvP are both permitted. You will see it in the Community section of the server browser, since it is a community server. Carbon plugins are running on it. The vanilla label is its own: nothing is altered here: rates, kits and rules are as Facepunch ships them. VAC, Valve's anti-cheat, is enabled.
Can you tell me which map [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly uses?
The game generates the procedural map on [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly at size 1,400 with 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 [NL][EU] SPE | OneGrid | Vanilla | Solo/Duo/Trio | Bi-Weekly?
Enter client.connect 31.184.89.136:28015 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically.
Server tags
what each one means
Published asmp30,ptrak,$r?,v2633,^y,^b,^v,EU,gmrust,cs163794,ts3
Game
gmrust
Game modeRust survival, played by the standard rules.
mp30
Max playersThe server holds 30 slots.
ts3
Group limitTeams cap out at 3.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildThis runs on build 163794.
ptrak
NetworkingThe network layer is RakNet, standard for the game.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaNothing is altered here: rates, kits and rules are as Facepunch ships them.
Mods and access
^y
CarbonThe plugin framework in use is Carbon.
Region
EU
EuropeThe server browser lists it 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 standing (F); wipes are the one to work on (F).