RUST METRICSFlight deck · live data
Data live Servers11,845 Players80,760 Populated3,897 Fresh wipes 3 h164 Scan5 min
‹ All servers178.57.59.176:28015
Offline Full Queue Fresh wipe Wipe due No query

Timeweb Cloud

Offline 178.57.59.176:28015 checked 2d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 1.2 2.5 3.8 5 PAX 1 /5

Players now

20% full 7-day avg7-day peak
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 average1peak 1
Rank#11,528top 52%
Last wipe2d 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
15k10k15k20k25 Oct26 Oct27 Oct

Top 52% 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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Sun 25 Oct, 08:27 UTC2d 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 should you expect from wipe day on Timeweb Cloud?

The busiest point of its recent wipes drew 1 players on average. After the latest wipe, numbers topped out at 0 hours.

When does Timeweb Cloud wipe?

Its rhythm cannot be told from the wipes of Timeweb Cloud on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 2 days 12 hours ago the current world was made.

Tag meanings

Which tags does Timeweb Cloud carry, and what do they mean?

Tags published by Timeweb Cloud, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): The server holds 5 slots; ts8 (Group limit): The game default applies: teams of up to 8; v2635 (Protocol): Match the game version: protocol 2635 is required; cs168909 (Build): Build 168909; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): The region field is empty. Reading the top of this page: the tags also hold the current players, the queue and when the world was made.

Which lists and filters on Rust Metrics show Timeweb Cloud?

On Rust Metrics, Timeweb Cloud 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 3 days.

Population

What position does Timeweb Cloud hold among Rust servers?

Ranking for Timeweb Cloud: #11,528 on seven-day player hours, top 52% of all ranked servers.

How full does Timeweb Cloud get?

Status for Timeweb Cloud: offline. Last seen 2 days 11 hours ago. Seven-day check: 1 players on average. Peak reading: 1.

Operator and location

Which location does Timeweb Cloud run from?

Reading: location. Timeweb Cloud gives no region. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 178.57.59.176:28015.

What Rust version is Timeweb Cloud on?

Version check: Rust network protocol 2635 and build 168909 on Windows, run by Timeweb Cloud. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Timeweb Cloud, and is it online?

Check: connection. Timeweb Cloud is offline at this moment. Last contact was 2 days 11 hours ago. Uptime for the last 1 full day: 0 of 24 hours, or 0%. Check: first contact. Rust Metrics logged it on 25 October 2026.

Rules and settings

How is Timeweb Cloud configured, and what rules are in force?

Check: gather rate. The name Timeweb Cloud does not state one. 8 players per group, the default value. survival, gather, build and raid, as the game normally runs — that is the game mode. Combat and raiding against other players are on. Under Community in the server browser you will find it. VAC is on. That is Valve's anti-cheat.

Which map is live on Timeweb Cloud?

Procedural map on Timeweb Cloud, made by the game's generator.

How to join

What do you do to join Timeweb Cloud?

To join: start Rust, press F1 and type client.connect 178.57.59.176:28015. Or press Launch Rust here and Steam opens the game and connects you.

PLACARDS

Server tags

what each one means

Published as mp5,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players The server holds 5 slots.
ts8
Group limit The game default applies: teams of up to 8.
v2635
Protocol Match the game version: protocol 2635 is required.
cs168909
Build Build 168909.
ptrak
Networking Network layer: RakNet, the standard for the game.
$r?
Region code The region field is empty.

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.