Working its way up from the back of the class: #15,960 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
53/ 100
D
Moving up: up 879 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 71% of all ranked servers. 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 Thursday 29 October, 18:19 UTC, in 3h.
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 what location does ZipClaw Biweekly | PVE | для новичков sit?
You won't find a region tag on ZipClaw Biweekly | PVE | для новичков, but its name indicates Europe. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 93.123.156.69:28010.
How dependable is ZipClaw Biweekly | PVE | для новичков, and is it online at the moment?
You cannot join now: ZipClaw Biweekly | PVE | для новичков is offline, last seen 23 days 6 hours ago. For the last 7 full days, it was up 0 of 168 hours, or 0% of the time. On 6 October 2026, Rust Server Score saw it for the first time.
On what Rust version does ZipClaw Biweekly | PVE | для новичков sit?
Rust network protocol 2634 and build 166494 on Linux is what ZipClaw Biweekly | PVE | для новичков runs. You need the same protocol to join; Steam takes care of updating your game.
Wipe schedule
On what schedule does ZipClaw Biweekly | PVE | для новичков reset?
The next wipe on ZipClaw Biweekly | PVE | для новичков is a projection from biweekly: 14 days after its last wipe. It is due to wipe next on Thursday 29 October at 18:19 UTC. It has been running its current world for 27 days 20 hours. Its tags say it wipes every two weeks.
Population
What position does ZipClaw Biweekly | PVE | для новичков hold in the rankings?
In the top 71% of all ranked servers, ZipClaw Biweekly | PVE | для новичков sits at #15,960 for player hours over the last seven days.
How many players does ZipClaw Biweekly | PVE | для новичков usually have?
The last sighting of ZipClaw Biweekly | PVE | для новичков was 23 days 6 hours ago, and it is offline right now.
Tags
How should you read the tags on ZipClaw Biweekly | PVE | для новичков?
You'll see ZipClaw Biweekly | PVE | для новичков tagged with gmrust (Game mode): This one runs plain Rust survival, with nothing altered; mp100 (Max players): 100 slots are available; ts5 (Group limit): No team may go above 5; v2634 (Protocol): Join only if your game runs protocol 2634; cs166494 (Build): This runs on build 166494; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^b (Biweekly): A wipe happens once a fortnight; ^s (Softcore): On death you keep part of your inventory: that is Facepunch's easier mode; ^t (Tutorial on): Facepunch's tutorial gives new players a starting point here; ^p (PvE): This is player against world: players do not fight each other; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Because settings or plugins change how it plays, it is listed as Modded 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.
Which lists and filters on Rust Server Score show ZipClaw Biweekly | PVE | для новичков?
These Rust Server Score lists count ZipClaw Biweekly | PVE | для новичков among them: Rust tutorial servers, graded, European Rust servers, graded, Modded Rust servers, graded and Rust PvE servers, graded. You can find it under these server-list filters: Region: Europe; Type: Modded; Game mode: PvE and Softcore; Server tag: Biweekly ^b, Softcore ^s, PvE ^p, Tutorial on ^t, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks.
Rules and settings
How is ZipClaw Biweekly | PVE | для новичков set up, and what rules does it keep?
The name of ZipClaw Biweekly | PVE | для новичков gives no gather rate. The limit for a group is 5 players. It runs softcore, Facepunch's easier setting, with part of your loot kept. Fighting and raiding between players are both allowed. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. The server runs Valve's anti-cheat, VAC.
Which map is in play on ZipClaw Biweekly | PVE | для новичков?
ZipClaw Biweekly | PVE | для новичков runs a procedural map, which the game generates.
Connecting
How do you get onto ZipClaw Biweekly | PVE | для новичков?
Enter client.connect 93.123.156.69:28010 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 asmp100,ptrak,$r?,v2634,^b,^s,^t,^p,gmrust,cs166494,ts5,^o^z
Game
gmrust
Game modeThis one runs plain Rust survival, with nothing altered.
mp100
Max players100 slots are available.
ts5
Group limitNo team may go above 5.
v2634
ProtocolJoin only if your game runs protocol 2634.
cs166494
BuildThis runs on build 166494.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Wipe schedule
^b
BiweeklyA wipe happens once a fortnight.
Difficulty
^s
SoftcoreOn death you keep part of your inventory: that is Facepunch's easier mode.
Gameplay
^t
Tutorial onFacepunch's tutorial gives new players a starting point here.
^p
PvEThis is player against world: players do not fight each other.
Mods and access
^o
OxideThe plugin framework in use is Oxide (uMod).
^z
ModdedBecause settings or plugins change how it plays, it is listed as Modded.
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).