RUST METRICSFlight deck · live data
Data live Servers11,701 Players40,419 Populated3,002 Fresh wipes 3 h95 Scan5 min
‹ All servers103.7.206.245:28015
Offline Full Queue Fresh wipe Wipe due No query

Tom's Local Rust

Offline 103.7.206.245:28015 checked 19d ago

COM 1 · connect

Server instruments

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

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,632top 71%
Last wipe19d agono schedule published
Next wipe–no wipe 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
15k10k15k20k9 Oct10 Oct12 Oct13 Oct15 Oct16 Oct

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

PLAN

Wipe schedule

Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.

LOG

Wipes

newest first
WipedPeakCrowdLastedPlayers before
No wipe seen yet.

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 wipe timing does Tom's Local Rust follow?

Its rhythm cannot be told from the wipes of Tom's Local Rust 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. 19 days 3 hours ago the current world was made.

Tag meanings

How should you read the tags on Tom's Local Rust?

These are the tags Tom's Local Rust publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp1 (Max players): 1 slots in total; ts8 (Group limit): Team cap of 8, which is the game default; v2634 (Protocol): Protocol 2634: join only on the same game version; cs167398 (Build): Build 167398; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set. 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 Tom's Local Rust?

On Rust Metrics, Tom's Local Rust sits in these lists: Rust community servers: live readings. These filters bring it up on the server list: Type: Community (not modded, not official) and No plugins at all; Group limit: 5 or more.

Population

What position does Tom's Local Rust hold among Rust servers?

Player hours over seven days put Tom's Local Rust at #15,632, in the top 71% of all ranked servers.

What player count does Tom's Local Rust carry?

Tom's Local Rust is not responding; status offline, last seen 19 days 2 hours ago.

Server

Which location does Tom's Local Rust run from?

No region comes from Tom's Local Rust. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Connect using 103.7.206.245:28015.

What Rust version is Tom's Local Rust on?

Rust network protocol 2634 and build 167398 on Windows is the build Tom's Local Rust runs. To get in, your game needs the same protocol; Steam applies the update.

What is the uptime on Tom's Local Rust, and is it online?

Reading: offline. Tom's Local Rust last answered 19 days 2 hours ago. Uptime for the last 7 full days: 0 of 168 hours, or 0%. The first sighting on Rust Metrics was 9 October 2026.

Settings and map

What settings and rules apply on Tom's Local Rust?

Check: gather rate. The name Tom's Local Rust does not state one. 8 players per group, the default value. Mode check gives survival; the normal game: build, gather, raid. Combat and raiding against other players are on. Listing: Community server. Check: anti-cheat. VAC, Valve's system, is off.

What map is Tom's Local Rust on?

Check: map. Procedural, generated by the game, on Tom's Local Rust.

How to join

How do you connect to Tom's Local Rust?

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

PLACARDS

Server tags

what each one means

Published as mp1,ptrak,$r?,v2634,gmrust,cs167398,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp1
Max players 1 slots in total.
ts8
Group limit Team cap of 8, which is the game default.
v2634
Protocol Protocol 2634: join only on the same game version.
cs167398
Build Build 167398.
ptrak
Networking RakNet carries the traffic, as standard for Rust.
$r?
Region code Region code: none 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.