RUST METRICSFlight deck · live data
Data live Servers11,758 Players58,600 Populated3,466 Fresh wipes 3 h131 Scan5 min
‹ All servers92.51.18.124:28015
Offline Full Queue Fresh wipe Wipe due No query

Timeweb Cloud

Offline 92.51.18.124:28015 checked 8d ago

COM 1 · connect

Server instruments

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

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,366top 70%
Last wipe8d 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 Oct21 Oct23 Oct24 Oct26 Oct27 Oct

Top 70% 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 peak0players, last three wipes

The first 48 hours of its last wipes

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 20 Oct, 17:49 UTC8d ago 0 – 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

Reset cycle

What happens on Timeweb Cloud when wipe day comes?

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

When does Timeweb Cloud wipe?

To tell the rhythm of Timeweb Cloud, too few of its wipes are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 8 days 4 hours ago the current world was made.

Tag meanings

How should you read the tags on Timeweb Cloud?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp5 (Max players): Slots: 5; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Your game must run protocol 2634 to get in; cs167781 (Build): Game build reading: 167781; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Timeweb Cloud. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Where does Timeweb Cloud appear in Rust Metrics lists and filters?

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

Occupancy

What position does Timeweb Cloud hold among Rust servers?

Ranking for Timeweb Cloud: #15,366 on seven-day player hours, top 70% of all ranked servers.

How full does Timeweb Cloud get?

Status for Timeweb Cloud: offline. Last seen 8 days 4 hours ago.

Server details

What location is Timeweb Cloud hosted in?

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. Check: address. It reads 92.51.18.124:28015.

What Rust version is Timeweb Cloud on?

Version check: Rust network protocol 2634 and build 167781 on Windows, run by Timeweb Cloud. Matching protocol is required to join. Let Steam update your game.

How reliable is Timeweb Cloud, and is it online now?

Timeweb Cloud reports offline. The last reading came 8 days 4 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. Check: first contact. Rust Metrics logged it on 20 October 2026.

Rules and settings

What settings and rules apply on Timeweb Cloud?

Reading the name gives no gather rate for Timeweb Cloud. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: gather, build and raid, as the game normally runs. Players can raid each other and fight. That is permitted here. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is Timeweb Cloud on?

Check: map. Procedural, generated by the game, on Timeweb Cloud.

How to join

How can you get onto Timeweb Cloud?

Press F1 in Rust and enter client.connect 92.51.18.124:28015. You can also use Launch Rust on this page, which passes you to Steam to open Rust and connect.

PLACARDS

Server tags

what each one means

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

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players Slots: 5.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Your game must run protocol 2634 to get in.
cs167781
Build Game build reading: 167781.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code No region code is 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.