Working its way up from the back of the class: #13,597 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
33/ 100
F
Needs to keep more players after wipe day: 33% of wipes kept half their crowd.
Momentumrank now against a week ago
30/ 100
F
Lost ground: down 5,542 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 62% of all ranked servers. Ranked on player hours over the last seven days.
Attendance: the wipe record
5 wipe days in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
·······
·······
W·WW···
······W
····W··
·······
·······
····
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
no rhythm it keeps
Its wipes keep no rhythm, so there is no next wipe to predict. Every server wipes at the monthly force wipe.
usual gap3.6 daysbetween real wipes
on rhythm0%of its recent wipes
wipe-day peak1players, last three wipes
crowd held33%else halves by day 6
The first 48 hours of its last wipes
Fri 9 OctSun 4 OctThu 24 Sep
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
Fri 9 Oct, 15:59 UTC19d ago
1
–
running
0
Sun 4 Oct, 16:55 UTC24d ago
1
halved by day 3
5 days
0
Thu 24 Sep, 16:24 UTC34d ago
1
halved by day 9
10 days
0
Wed 23 Sep, 16:16 UTC35d ago
1
–
1 days
1
Mon 21 Sep, 09:15 UTC37d ago
1
✓ held half
2.3 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
WipeZoquixerServ leaves the region unpublished. Rust Server Score takes the server's word for its location and does not trace the hardware. Find it at 37.194.107.140:28015.
How reliable is WipeZoquixerServ, and is it up?
The server is down: WipeZoquixerServ is offline now, with the last sighting 18 days 23 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. On 20 September 2026, Rust Server Score saw it for the first time.
What Rust version is WipeZoquixerServ on?
You will find WipeZoquixerServ on Rust network protocol 2634 and build 166652, hosted on Windows. Steam updates your game for you, but you need the same protocol to join.
Wipe cycle
How frequently does WipeZoquixerServ wipe its map?
WipeZoquixerServ wipes at times that vary, so no next wipe can be predicted. Next up is Thursday 5 November at 19:00 UTC, when the monthly force wipe takes every Rust server with it. The world it runs now was created 19 days 16 hours.
What should you expect from wipe day on WipeZoquixerServ?
Across its recent wipes, the busiest moments averaged 1 players. The crowd on the latest wipe was largest 1 hours after it began. Half the peak held until the next wipe in 33% of its recent wipes. In the other wipes it slipped under half by day 6.
Population
What position does WipeZoquixerServ hold in the rankings?
Over the last seven days, WipeZoquixerServ has #13,597 for player hours, in the top 62% of all ranked servers.
What does the population on WipeZoquixerServ look like?
It has been 18 days 23 hours since WipeZoquixerServ was last seen, and it is offline right now.
Tags and filters
What do WipeZoquixerServ's tags stand for?
gmrust (Game mode): Rust survival, played by the standard rules; mp3 (Max players): 3 slots are available; ts8 (Group limit): The limit is 8 per team, the default the game ships with; v2634 (Protocol): Join only if your game runs protocol 2634; cs166652 (Build): This runs on build 166652; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): No region code has been set are the tags WipeZoquixerServ 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.
Where does WipeZoquixerServ appear in the Rust Server Score lists and filters?
These Rust Server Score lists count WipeZoquixerServ 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
Which rules does WipeZoquixerServ enforce, and what are its settings?
Nothing in the name of WipeZoquixerServ states a gather rate. With no change from the game default, groups take up to 8 players. survival is the mode here, gather and build and raid: the standard game. Fighting and raiding between players are both allowed. The server browser lists it under Community, as a community server. The server runs Valve's anti-cheat, VAC.
Which map is in play on WipeZoquixerServ?
A procedural map, generated by the game, is what WipeZoquixerServ runs.
Connecting
How should you connect to WipeZoquixerServ?
To connect, start Rust, press F1, and type client.connect 37.194.107.140:28015. Or click Launch Rust here, which launches Rust through Steam and joins you.
Server tags
what each one means
Published asmp3,ptrak,$r?,v2634,gmrust,cs166652,ts8
Game
gmrust
Game modeRust survival, played by the standard rules.
mp3
Max players3 slots are available.
ts8
Group limitThe limit is 8 per team, the default the game ships with.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166652
BuildThis runs on build 166652.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$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. Even marks across the subjects, from F to F.