RUST METRICSFlight deck · live data
Data live Servers11,802 Players69,058 Populated3,653 Fresh wipes 3 h129 Scan5 min
‹ All servers188.243.182.39:28015
Offline Full Queue Fresh wipe Wipe due No query

Timeweb Cloud

Offline 188.243.182.39:28015 checked 16d 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,509top 71%
Last wipe16d 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
15k10k15k20k21 Sep25 Sep29 Sep2 Oct15 Oct19 Oct

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

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

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

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
Mon 12 Oct, 15:46 UTC16d 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

Wipe schedule

What should you expect from wipe day on Timeweb Cloud?

An average of 0 players came at the busiest on its recent wipes. 0 hours after the wipe, the crowd peaked on the latest wipe.

How often does Timeweb Cloud wipe, and when?

Its rhythm cannot be told from the wipes of Timeweb Cloud on record: there are too few. 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 16 days 5 hours ago.

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): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs167584 (Build): Game build reading: 167584; 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.

Player count

What position does Timeweb Cloud hold among Rust servers?

Player hours over seven days put Timeweb Cloud at #15,509, in the top 71% of all ranked servers.

What is the population on Timeweb Cloud?

Status for Timeweb Cloud: offline. Last seen 16 days 5 hours ago.

Server

Which location does Timeweb Cloud run from?

No region tag on Timeweb Cloud. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 188.243.182.39:28015.

What Rust version is Timeweb Cloud on?

Reading: Timeweb Cloud, Rust network protocol 2634 and build 167584, Windows. Check: protocol. To join, your game must match; Steam handles the update.

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

Timeweb Cloud reports offline. The last reading came 16 days 5 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 21 September 2026.

Settings and map

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

Reading the name gives no gather rate for Timeweb Cloud. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. 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.

Which map is live on Timeweb Cloud?

The game generates a procedural map for Timeweb Cloud.

Join

How do you connect to Timeweb Cloud?

Press F1 in Rust and enter client.connect 188.243.182.39: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,cs167584,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp5
Max players 5 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs167584
Build Game build reading: 167584.
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.