RUST METRICSFlight deck · live data
Data live Servers11,682 Players55,436 Populated3,376 Fresh wipes 3 h100 Scan5 min
‹ All servers89.161.42.181:28015
Offline Full Queue Fresh wipe Wipe due No query

zibo2020

Offline 89.161.42.181:28015 checked 6d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 50 100 150 200 PAX 0 /200

Players now

0% full 7-day avg
0 10 30 60 120 256 FPS – – – SERVER FPS OFF

Server fps

no direct query answered in 48 hours
0 ENT – – – ×1000 OFF

Entities

no direct query answered in 48 hours
1239 ET SINCE RESTART – – : – – OFF

Uptime

no direct query answered in 48 hours
7-day average0peak –
Rank#15,399top 69%
Last wipe7d agono schedule published
Next wipe–too few wipes seen yet
Memory–at the last reading
REC 1

Players

No hourly history yet.

Hourly average and peak, UTC.

REC 2

Server performance

This server has not answered a direct query in the last 48 hours.

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.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k20 Oct22 Oct23 Oct25 Oct26 Oct28 Oct

Top 69% of all ranked servers. Ranked on player hours over the last seven days.

PLAN

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

01234+0h+9h+19h+28h+38h+47h

Players each hour, from the hour of the wipe. The latest peaked at 1, 1 hours in.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Wed 21 Oct, 07:58 UTC7d 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.

ALTN

Similar servers

the same kind of game, then region, group limit, rate and wipes
QRH

Quick answers

from the figures on this page

Wipe timing

What happens on zibo2020 when wipe day comes?

At their busiest, its recent wipes drew 1 players on average. Peak crowd on the latest wipe: 1 hours in.

How often does zibo2020 wipe, and when?

The rhythm of zibo2020's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. The world it runs now was made 7 days 2 hours ago.

Tag meanings

Which tags does zibo2020 carry, and what do they mean?

Tags published by zibo2020, read by the game's server browser: gmrust (Game mode): Survival, as standard Rust plays it; mp200 (Max players): Slots: 200; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does zibo2020 appear in Rust Metrics lists and filters?

On Rust Metrics, zibo2020 sits in these lists: Rust community servers: live readings. Reading: server list filters. It comes up under Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more; Last wipe: In the last 2 weeks.

Player count

What position does zibo2020 hold among Rust servers?

Player hours over seven days put zibo2020 at #15,399, in the top 69% of all ranked servers.

How full does zibo2020 get?

Status for zibo2020: offline. Last seen 6 days 12 hours ago. Check: player average. 0 over the last seven days.

Operator and location

Where does zibo2020 sit?

No region comes from zibo2020. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 89.161.42.181:28015.

What Rust version is zibo2020 on?

Reading: zibo2020, Rust network protocol 2634 and build 167781, Windows. Matching protocol is required to join. Let Steam update your game.

How reliable is zibo2020, and is it online now?

Check: connection. zibo2020 is offline at this moment. Last contact was 6 days 12 hours ago. Uptime for the last 7 full days: 22 of 168 hours, or 13%. Check: first contact. Rust Metrics logged it on 20 October 2026.

Settings and map

What settings and rules apply on zibo2020?

Reading the name gives no gather rate for zibo2020. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. Anti-cheat reading: VAC off, Valve's system.

What map is zibo2020 on?

The game generates a procedural map for zibo2020.

How to join

How do you connect to zibo2020?

Check: join. Open Rust, press F1, then enter client.connect 89.161.42.181:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp200,ptrak,$r?,v2634,gmrust,cs167781,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp200
Max players Slots: 200.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167781
Build Game build reading: 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.