ZCheckServer
Offline 157.85.89.95:28855 checked 33d ago
Players
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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 bestWipe schedule
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force 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
the same kind of game, then region, group limit, rate and wipes
- 1000/ 100
- 80/ 400
- 91/ 245
- 127/ 100
- 192/ 1000
- 17/ 700
Quick answers
Tags and filters
Where does ZCheckServer appear in Rust Going Deep lists and filters?
These Rust Going Deep lists include ZCheckServer: Modded Rust servers. The server list shows it under Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
What's the meaning of the tags on ZCheckServer?
The server browser shows these tags for ZCheckServer: gmrust (Game mode): This is the standard Rust survival experience; mp22 (Max players): The slot count is 22; ts8 (Group limit): The default team size of 8 applies here; v2633 (Protocol): To join, your game has to be on protocol 2633; cs163794 (Build): This server runs build 163794; ptrak (Networking): RakNet, the network layer Rust uses by default; $r? (Region code): No region is set; ^o (Oxide): The plugin framework here is Oxide (uMod); ^z (Modded): Plugins or settings make changes, so it's listed as Modded. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
About the server
What's the location of ZCheckServer?
ZCheckServer does not put out a region. Where a server says it is, that is what Rust Going Deep shows — no lookup of the machine's real spot. The endpoint is 157.85.89.95:28855.
How reliable is ZCheckServer?
The server ZCheckServer is not reachable at the moment; the last sighting was 33 days 9 hours ago. In the last full 7 days, 0 of 168 hours were online, 0% uptime. 13 September 2026 is when Rust Going Deep first saw it.
What is the Rust version for ZCheckServer?
Rust network protocol 2633 and build 163794 is what ZCheckServer runs, on Linux. To join, your game must be on the same protocol; Steam takes care of updating it.
Wipe schedule
When does ZCheckServer wipe?
Too few wipes are on record for ZCheckServer to show its rhythm. Next on Thursday 5 November at 19:00 UTC: the force wipe that all Rust servers take every month. This world has been running since 36 days 22 hours ago.
Map and rules
What settings and rules have been applied to ZCheckServer?
No gather rate appears in the name of ZCheckServer. The group limit is the game's default of 8 players. survival is the game mode, gather, build and raid, the standard game. Fighting and raiding between players is allowed. In the server browser it sits under Modded, where plugins or settings change the game. Oxide plugins are running here. The server runs Valve's anti-cheat, VAC.
What's the map on ZCheckServer?
The map on ZCheckServer is procedural, made by the game.
Player stats
Is ZCheckServer busy?
ZCheckServer was last seen 33 days 9 hours ago and is offline as you read this.
What position does ZCheckServer hold in the server rankings?
For player hours in the last seven days, ZCheckServer ranks #15,015, within the top – of ranked servers.
Join info
How do you get into ZCheckServer?
Open Rust and press F1, then type client.connect 157.85.89.95:28855. Alternatively, click Launch Rust on this page to join via Steam.