RUST METRICSFlight deck · live data
Data live Servers11,644 Players39,508 Populated2,969 Fresh wipes 3 h74 Scan5 min
‹ All servers152.233.43.67:28015
Offline Full Queue Fresh wipe Wipe due No query

Timeweb Cloud

Offline 152.233.43.67:28015 checked 28d 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#16,201top 68%
Last wipe28d 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 Sep27 Sep29 Sep2 Oct4 Oct6 Oct

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

No hourly players around its wipes yet.

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Tue 29 Sep, 18:10 UTC28d 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. 0 hours after the wipe, the crowd peaked on the latest wipe.

When does Timeweb Cloud wipe?

The rhythm of Timeweb Cloud's wipes cannot be told yet: too few are on record. The monthly force wipe is when every Rust server wipes, and the next one is on Thursday 5 November at 19:00 UTC. The world in play was created 28 days 8 hours ago.

Tag meanings

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

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp5 (Max players): 5 slots in total; ts8 (Group limit): The game default applies: teams of up to 8; v2633 (Protocol): Protocol 2633: join only on the same game version; cs165217 (Build): Game build reading: 165217; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): No region code is set from Timeweb Cloud. 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. 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.

Occupancy

Where does Timeweb Cloud sit in the rankings?

Ranking for Timeweb Cloud: #16,201 on seven-day player hours, top 68% of all ranked servers.

How full does Timeweb Cloud get?

Timeweb Cloud is not responding; status offline, last seen 28 days 8 hours ago.

Operator and location

Where does Timeweb Cloud sit?

No region tag on Timeweb Cloud. Rust Metrics does not look up where the machine stands; it shows where the server says it is. The endpoint you need is 152.233.43.67:28015.

What Rust version is Timeweb Cloud on?

Rust network protocol 2633 and build 165217 on Windows is the build Timeweb Cloud runs. To get in, your game needs the same protocol; Steam applies the update.

Is Timeweb Cloud up, and how often does it stay up?

Timeweb Cloud reports offline. The last reading came 28 days 8 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Check: first contact. Rust Metrics logged it on 25 September 2026.

Settings and map

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

No gather rate appears in the name: Timeweb Cloud. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Players can raid each other and fight. That is permitted here. 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?

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

Connection

How can you get onto Timeweb Cloud?

Press F1 in Rust and enter client.connect 152.233.43.67: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?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp5
Max players 5 slots in total.
ts8
Group limit The game default applies: teams of up to 8.
v2633
Protocol Protocol 2633: join only on the same game version.
cs165217
Build Game build reading: 165217.
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.