Working its way up from the back of the class: #15,561 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 220 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.
No daily history yet.
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. Ranked on player hours over the last seven days.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
··
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 11 Oct, 15:42 UTC16d ago
1
–
running
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
EACPatchTest leaves the region unpublished. The location shown on Rust Server Score comes from the server itself, not from a lookup of the machine. 85.175.226.51:29000 is the address to use.
How reliable is EACPatchTest, and is it up?
At this moment, EACPatchTest is offline; the last time it was seen was 16 days 1 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. It was first seen by Rust Server Score on 11 October 2026.
On what Rust version does EACPatchTest sit?
Rust network protocol 2634 and build 167398 on Windows is what EACPatchTest runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
How frequently does EACPatchTest wipe its map?
The record holds too few of EACPatchTest's wipes to tell its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 16 days 2 hours.
What happens on EACPatchTest when wipe day arrives?
Recent wipes have peaked at 1 players on average. Peak numbers came 1 hours into the latest wipe.
Player count
What position does EACPatchTest hold in the rankings?
In the top 70% of all ranked servers, EACPatchTest sits at #15,561 for player hours over the last seven days.
How many players does EACPatchTest usually have?
It has been 16 days 1 hours since EACPatchTest was last seen, and it is offline right now.
Tags
What do EACPatchTest's tags stand for?
gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp50 (Max players): Its slot count is 50; ts8 (Group limit): Teams are capped at 8, the game's standard setting; v2634 (Protocol): The game protocol is 2634, so your game must match that version to join; cs167398 (Build): This runs on build 167398; ptrak (Networking): RakNet handles it, the game's default network layer; $r? (Region code): No region code has been set are the tags EACPatchTest publishes, and the game's server browser reads them. 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.
Which Rust Server Score filters and lists feature EACPatchTest?
These Rust Server Score lists count EACPatchTest among them: Best community servers, graded. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.
Map and rules
What settings and rules apply on EACPatchTest?
The name of EACPatchTest gives no gather rate. The default of 8 players applies as the group cap. 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 under Community, as a community server. VAC, Valve's anti-cheat, is enabled.
EACPatchTest runs which map?
A procedural map, generated by the game, is what EACPatchTest runs.
How to join
What is the way to join EACPatchTest?
Enter client.connect 85.175.226.51:29000 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 asmp50,ptrak,$r?,v2634,gmrust,cs167398,ts8
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp50
Max playersIts slot count is 50.
ts8
Group limitTeams are capped at 8, the game's standard setting.
v2634
ProtocolThe game protocol is 2634, so your game must match that version to join.
cs167398
BuildThis runs on build 167398.
ptrak
NetworkingRakNet handles it, the game's default network layer.
$r?
Region codeNo region code has been set.
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).