Working its way up from the back of the class: #15,123 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
26/ 100
F
Lost ground: down 7,159 places this week. A strong wipe could turn it round.
A term to build on.
Even marks across the subjects, from F to 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.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 70% of all ranked servers, top 88% in EU, and #526 of the trio servers (top 85%). Ranked on player hours over the last seven days.
Attendance: the wipe record
11 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·····WW
·WWW··W
WWWWW··
·······
····
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, 17:37 UTC, in 1d 10h.
Its weekly schedule tag · low confidence
usual gap0.5 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
Coming wipes
1d 10hFri 30 Oct, 17:37 UTC
7d 11hThu 5 Nov, 19:00 UTCFW
8d 10hFri 6 Nov, 17:37 UTC
15d 10hFri 13 Nov, 17:37 UTC
22d 10hFri 20 Nov, 17:37 UTC
29d 10hFri 27 Nov, 17:37 UTC
35d 11hThu 3 Dec, 19:00 UTCFW
36d 10hFri 4 Dec, 17:37 UTC
The first 48 hours of its last wipes
Fri 16 OctThu 15 OctThu 15 Oct
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
Fri 16 Oct, 17:37 UTC12d ago
0
–
running
0
Thu 15 Oct, 18:44 UTC13d ago
1
–
1 days
0
Thu 15 Oct, 09:06 UTC13d ago
1
–
0.4 days
1
Wed 14 Oct, 17:58 UTC14d ago
1
–
0.6 days
0
Wed 14 Oct, 10:04 UTC14d ago
1
–
0.3 days
0
Tue 13 Oct, 20:10 UTC15d ago
1
–
0.6 days
0
Mon 12 Oct, 21:04 UTC16d ago
1
–
1 days
1
Mon 12 Oct, 15:01 UTC16d ago
1
–
0.3 days
0
Mon 12 Oct, 08:17 UTC16d ago
1
–
0.3 days
0
Sun 11 Oct, 20:36 UTC17d ago
1
–
0.5 days
0
Thu 8 Oct, 07:19 UTC20d ago
0
–
3.6 days
0
Wed 7 Oct, 22:11 UTC21d ago
0
–
0.4 days
0
Wed 7 Oct, 10:43 UTC21d ago
0
–
0.5 days
0
Tue 6 Oct, 22:05 UTC22d ago
0
–
0.5 days
1
Tue 6 Oct, 15:52 UTC22d ago
1
–
0.3 days
0
Sun 4 Oct, 20:29 UTC24d ago
0
–
1.8 days
0
Sat 3 Oct, 23:18 UTC25d ago
0
–
0.9 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 [WILDCORE] EU 2X | TEST | JUST WIPED based in?
You'll see [WILDCORE] EU 2X | TEST | JUST WIPED listed in Europe, tagged EU. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 193.141.60.251:28015 is the address to use.
Is [WILDCORE] EU 2X | TEST | JUST WIPED up, and how steady is its uptime?
The server is down: [WILDCORE] EU 2X | TEST | JUST WIPED is offline now, with the last sighting 12 days 8 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 27 September 2026, Rust Server Score saw it for the first time.
On what Rust version does [WILDCORE] EU 2X | TEST | JUST WIPED sit?
Rust network protocol 2634 and build 167781 on Linux is what [WILDCORE] EU 2X | TEST | JUST WIPED runs. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
When does [WILDCORE] EU 2X | TEST | JUST WIPED wipe, and how often?
Too few wipes on [WILDCORE] EU 2X | TEST | JUST WIPED are recorded to confirm the schedule, so its tag guides the prediction. Friday 30 October at 17:37 UTC is the date set for its next wipe. It has been running its current world for 12 days 13 hours. Wipes are scheduled weekly, according to its tags.
What happens on [WILDCORE] EU 2X | TEST | JUST WIPED when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 0 hours into the latest wipe.
Player numbers
Where does [WILDCORE] EU 2X | TEST | JUST WIPED place in the wider field of Rust servers?
In Europe, [WILDCORE] EU 2X | TEST | JUST WIPED is #2,598, and overall it is #15,123 on player hours over the last seven days, in the top 70% of all ranked servers. It comes #526 among servers in the trio group.
What does the population on [WILDCORE] EU 2X | TEST | JUST WIPED look like?
[WILDCORE] EU 2X | TEST | JUST WIPED is offline at the moment; the last time it was seen was 12 days 8 hours ago.
Tags
How should you read the tags on [WILDCORE] EU 2X | TEST | JUST WIPED?
You'll see [WILDCORE] EU 2X | TEST | JUST WIPED tagged with gmrust (Game mode): Rust survival, played by the standard rules; mp2 (Max players): 2 slots are available; ts3 (Group limit): Teams cap out at 3; v2634 (Protocol): To get in, your game needs to be on the same version: the protocol is 2634; cs167781 (Build): Build number: 167781; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): A region code is not set here; ^w (Weekly): A wipe happens every week; ^v (Vanilla): You get the unmodified game: no rate changes, no kits, no rule changes; ^z (Modded): Plugins or settings alter the game, so it sits under Modded; ^y (Carbon): Carbon provides the plugin framework here; EU (Europe): In the server browser it appears under Europe in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Where does [WILDCORE] EU 2X | TEST | JUST WIPED appear in the Rust Server Score lists and filters?
Rust Server Score lists that include [WILDCORE] EU 2X | TEST | JUST WIPED: 2x Rust servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust servers with a trio group limit. These filters bring it up on the server list: Region: Europe; Type: Vanilla and Modded; Server tag: Weekly ^w, Vanilla ^v, Modded ^z and Carbon ^y; Group limit: Trio; Wipe schedule: Weekly; Last wipe: In the last 2 weeks; Gather rate: 2x.
Server rules
What settings and rules apply on [WILDCORE] EU 2X | TEST | JUST WIPED?
The name of [WILDCORE] EU 2X | TEST | JUST WIPED points to a 2x gather rate. The cap on group size is 3 players (trio). survival is the mode 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 Carbon. Vanilla is what it calls itself: you get the unmodified game: no rate changes, no kits, no rule changes. The server runs Valve's anti-cheat, VAC.
Can you tell me which map [WILDCORE] EU 2X | TEST | JUST WIPED uses?
[WILDCORE] EU 2X | TEST | JUST WIPED runs a procedural map, which the game generates.
How to join
How do you get onto [WILDCORE] EU 2X | TEST | JUST WIPED?
Enter client.connect 193.141.60.251: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 asmp2,ptrak,$r?,v2634,^z,^y,^w,^v,EU,gmrust,cs167781,ts3
Game
gmrust
Game modeRust survival, played by the standard rules.
mp2
Max players2 slots are available.
ts3
Group limitTeams cap out at 3.
v2634
ProtocolTo get in, your game needs to be on the same version: the protocol is 2634.
cs167781
BuildBuild number: 167781.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeA region code is not set here.
Wipe schedule
^w
WeeklyA wipe happens every week.
Difficulty
^v
VanillaYou get the unmodified game: no rate changes, no kits, no rule changes.
Mods and access
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
^y
CarbonCarbon provides the plugin framework here.
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. Even marks across the subjects, from F to F.