Working its way up from the back of the class: #15,482 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
50/ 100
D
Holding steady: up 121 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.
Average fpsLowest fpsWipe
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.
Average fpsLowest fpsWipe
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, measured since 21 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is best
RankRank in region
Top 67% of all ranked servers, top 84% in EU. Ranked on player hours over the last seven days.
Attendance: the wipe record
0 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
Next wipe Friday 30 October, 17:18 UTC, in 2d 16h.
Biweekly: 14 days after its last wipe
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
No wipe seen yet.
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 Europe, according to its own listing, sits Protocol 404 WiPe 04.09.26, with the EU tag. Rust Server Score reports the location a server gives; it does not check where the machine actually is. 178.185.89.92:28015 is the address to use.
How reliable is Protocol 404 WiPe 04.09.26, and is it up?
You cannot join now: Protocol 404 WiPe 04.09.26 is offline, last seen 36 days 7 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. It was first seen by Rust Server Score on 21 September 2026.
On what Rust version does Protocol 404 WiPe 04.09.26 sit?
You will find Protocol 404 WiPe 04.09.26 on Rust network protocol 2633 and build 163794, hosted on Windows. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does Protocol 404 WiPe 04.09.26 reset?
The estimate for Protocol 404 WiPe 04.09.26's next wipe comes from biweekly: 14 days after its last wipe. Friday 30 October at 17:18 UTC is the date set for its next wipe. The world it runs now was created 53 days 7 hours. Its tags say it wipes every two weeks.
Player count
Where does Protocol 404 WiPe 04.09.26 place in the wider field of Rust servers?
Over the last seven days, Protocol 404 WiPe 04.09.26 has #15,482 for player hours, in the top 67% of all ranked servers and #2,548 in Europe.
How many players does Protocol 404 WiPe 04.09.26 usually have?
It has been 36 days 7 hours since Protocol 404 WiPe 04.09.26 was last seen, and it is offline right now.
Tags
What do Protocol 404 WiPe 04.09.26's tags stand for?
You'll see Protocol 404 WiPe 04.09.26 tagged with gmrust (Game mode): Survival in the standard Rust style; mp100 (Max players): Its slot count is 100; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs163794 (Build): The game build is 163794; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set; ^b (Biweekly): A wipe happens once a fortnight; ^v (Vanilla): Facepunch's own version, with no changed rates, kits or rules; ^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.
Where does Protocol 404 WiPe 04.09.26 appear in the Rust Server Score lists and filters?
Rust Server Score lists that include Protocol 404 WiPe 04.09.26: European Rust servers, graded, Best community servers, graded and Vanilla Rust servers, graded. It shows under the following filters on the server list: Region: Europe; Type: Vanilla, Community (not modded, not official) and Plugins, not modded; Server tag: Biweekly ^b, Vanilla ^v and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Server rules
Which rules does Protocol 404 WiPe 04.09.26 enforce, and what are its settings?
The name of Protocol 404 WiPe 04.09.26 gives no gather rate. The group limit stays at the game's default of 8 players. 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. Oxide plugins are running on it. By its own description it is vanilla: facepunch's own version, with no changed rates, kits or rules. You are covered by VAC, Valve's anti-cheat.
Protocol 404 WiPe 04.09.26 runs which map?
A procedural map of size 5,600 and seed 10, generated by the game, is what Protocol 404 WiPe 04.09.26 runs. Because size and seed match, the map is the same each time, and this page links to it on RustMaps.
Getting in
What is the way to join Protocol 404 WiPe 04.09.26?
To connect, start Rust, press F1, and type client.connect 178.185.89.92:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp100,ptrak,$r?,v2633,^b,^v,EU,gmrust,cs163794,ts8,^o
Game
gmrust
Game modeSurvival in the standard Rust style.
mp100
Max playersIts slot count is 100.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs163794
BuildThe game build is 163794.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeNo region code has been set.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^v
VanillaFacepunch's own version, with no changed rates, kits or rules.
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 momentum (D); standing is the one to work on (F).