RUST METRICSFlight deck · live data
Data live Servers11,701 Players54,561 Populated3,263 Fresh wipes 3 h144 Scan5 min
‹ All servers83.71.46.198:28015
Offline Full Queue Fresh wipe Wipe due No query

Local Bot Server

Offline 83.71.46.198:28015 checked 43d ago

moddedcarbon
COM 1 · connect

Server instruments

no direct query in 48 hours
0 2 5 8 10 PAX 0 /10

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,464no region published
Last wipe43d 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
15k10k15k20k20 Sep21 Sep22 Sep
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 Local Bot Server follow?

The rhythm of Local Bot Server's wipes cannot be told yet: too few are on record. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 43 days 19 hours ago the current world was made.

Lists and filters

How should you read the tags on Local Bot Server?

These are the tags Local Bot Server publishes, and the server browser reads them: gmrust (Game mode): Survival, as standard Rust plays it; mp10 (Max players): The server holds 10 slots; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Match the game version: protocol 2633 is required; cs163794 (Build): Build 163794; ptrak (Networking): This is RakNet, Rust's usual network layer; $r? (Region code): No region code is set; ^z (Modded): Plugins or settings make this a modded server; ^y (Carbon): Carbon handles the plugins here. 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 Local Bot Server?

Rust Metrics lists featuring Local Bot Server: Modded Rust servers, checked live. Check: filters. On the server list it appears under these: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more.

Occupancy

What position does Local Bot Server hold among Rust servers?

Ranking for Local Bot Server: #15,464 on seven-day player hours, top – of all ranked servers.

How full does Local Bot Server get?

Status for Local Bot Server: offline. Last seen 43 days 14 hours ago.

Server details

Which location does Local Bot Server run from?

Reading: location. Local Bot Server 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 83.71.46.198:28015.

What Rust version is Local Bot Server on?

Rust network protocol 2633 and build 163794 on Windows is the build Local Bot Server runs. To get in, your game needs the same protocol; Steam applies the update.

How reliable is Local Bot Server, and is it online now?

Local Bot Server reports offline. The last reading came 43 days 14 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. Reading: first seen 15 September 2026, recorded by Rust Metrics.

Map and rules

What settings and rules apply on Local Bot Server?

Check: gather rate. The name Local Bot Server does not state one. No limit is set beyond the default. Groups take up to 8 players. survival, the normal game: build, gather, raid — that is the game mode. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Carbon plugins are running. Anti-cheat reading: VAC on, Valve's system.

What map is Local Bot Server on?

Procedural map on Local Bot Server, made by the game's generator.

Connection

What do you do to join Local Bot Server?

Press F1 in Rust and enter client.connect 83.71.46.198: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 mp10,ptrak,$r?,v2633,gmrust,cs163794,ts8,^z,^y

Game

gmrust
Game mode Survival, as standard Rust plays it.
mp10
Max players The server holds 10 slots.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Match the game version: protocol 2633 is required.
cs163794
Build Build 163794.
ptrak
Networking This is RakNet, Rust's usual network layer.
$r?
Region code No region code is set.

Mods and access

^z
Modded Plugins or settings make this a modded server.
^y
Carbon Carbon handles the plugins here.

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.