RUST METRICSFlight deck · live data
Data live Servers11,783 Players83,784 Populated3,853 Fresh wipes 3 h166 Scan5 min
‹ All servers46.110.178.155:28015
Offline Full Queue Fresh wipe Wipe due No query

TimoBeta

Offline 46.110.178.155:28015 checked 10d ago

COM 1 · connect

Server instruments

no direct query in 48 hours
0 0.2 0.5 0.8 1 PAX 1 /1

Players now

100% 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#13,072top 60%
Last wipe11d agono schedule published
Next wipe2d 2hFri 30 Oct, 17:31 UTC
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
15k10k15k20k1 Oct5 Oct10 Oct14 Oct20 Oct24 Oct

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

PLAN

Wipe schedule

fixed weekdays

Next wipe Friday 30 October, 17:31 UTC, in 2d 2h. Every other Friday at 17:31 UTC · low confidence

usual gap14 daysbetween real wipes
wipe-day peak1players, last three wipes
crowd held100%of its cycles kept half the crowd

Coming wipes

  1. WPT 1Fri 30 Oct, 17:31 UTC2d 2h
  2. WPT 2Thu 5 Nov, 19:00 UTC8d 3hFW
  3. WPT 3Fri 13 Nov, 17:31 UTC16d 2h
  4. WPT 4Fri 27 Nov, 17:31 UTC30d 2h
  5. WPT 5Thu 3 Dec, 19:00 UTC36d 3hFW
  6. WPT 6Fri 11 Dec, 17:31 UTC44d 2h

The first 48 hours of its last wipes

Fri 16 OctFri 2 Oct
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
Fri 16 Oct, 17:31 UTC11d ago 1 – running 1
Fri 2 Oct, 18:12 UTC25d ago 1 held half 14 days 1

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 TimoBeta when wipe day comes?

An average of 1 players came at the busiest on its recent wipes. After the latest wipe, numbers topped out at 0 hours. Above half that peak the crowd stayed until the next wipe in 100% of recent wipes.

When does TimoBeta wipe?

The wipe rhythm of TimoBeta is every other Friday at 17:31 UTC. Friday 30 October at 17:31 UTC is when its next wipe is due. The world in play was created 11 days 21 hours ago.

Lists and filters

How should you read the tags on TimoBeta?

Check: tags. The game's server browser reads gmrust (Game mode): Survival, as standard Rust plays it; mp1 (Max players): The server holds 1 slots; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166494 (Build): Game build reading: 166494; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from TimoBeta. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Which lists and filters on Rust Metrics show TimoBeta?

These Rust Metrics lists carry TimoBeta: 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

Where does TimoBeta sit in the rankings?

Ranking for TimoBeta: #13,072 on seven-day player hours, top 60% of all ranked servers.

What is the population on TimoBeta?

TimoBeta is not responding; status offline, last seen 10 days 15 hours ago.

Server

Which location does TimoBeta run from?

Reading: location. TimoBeta gives no region. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 46.110.178.155:28015.

What Rust version is TimoBeta on?

Reading: TimoBeta, Rust network protocol 2634 and build 166494, Windows. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on TimoBeta, and is it online?

Check: connection. TimoBeta is offline at this moment. Last contact was 10 days 15 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 1 October 2026.

Rules and settings

How is TimoBeta configured, and what rules are in force?

Reading the name gives no gather rate for TimoBeta. 8 players per group, the default value. Mode check gives survival; 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. VAC is on. That is Valve's anti-cheat.

Connection

How do you connect to TimoBeta?

Press F1 in Rust and enter client.connect 46.110.178.155: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 mp1,ptrak,$r?,v2634,gmrust,cs166494,ts8

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp1
Max players The server holds 1 slots.
ts8
Group limit Default limit in force: 8 per team.
v2634
Protocol Match the game version: protocol 2634 is required.
cs166494
Build Game build reading: 166494.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$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.