RUST METRICSFlight deck · live data
Data live Servers11,891 Players102,658 Populated3,942 Fresh wipes 3 h337 Scan5 min
‹ All servers203.220.108.50:28015
Offline Full Queue Fresh wipe Wipe due No query

A Slice of Rust

Offline 203.220.108.50:28015 checked 30d ago

COM 1 · connect

Server instruments

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

Players now

no slots published 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,866top 71%
Last wipe34d 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, measured since 28 Sep. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k28 Sep30 Sep1 Oct3 Oct4 Oct6 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

Reset cycle

When does A Slice of Rust wipe?

Its rhythm cannot be told from the wipes of A Slice of Rust on record: there are too few. On Thursday 5 November at 19:00 UTC the next monthly force wipe takes every Rust server, including this one. 34 days 16 hours ago the current world was made.

Tags

How should you read the tags on A Slice of Rust?

Tags published by A Slice of Rust, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp0 (Max players): Slots: 0; ts8 (Group limit): Default limit in force: 8 per team; v2633 (Protocol): Your game must run protocol 2633 to get in; cs165217 (Build): The server runs game build 165217; ptrak (Networking): Network layer: RakNet, the standard for the game; $r? (Region code): No region code is set. Check: the tags at the top of this page. They also carry players now, queue and world creation time.

Which lists and filters on Rust Metrics show A Slice of Rust?

On Rust Metrics, A Slice of 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.

Player count

What position does A Slice of Rust hold among Rust servers?

Player hours over seven days put A Slice of Rust at #16,866, in the top 71% of all ranked servers.

How full does A Slice of Rust get?

A Slice of Rust is not responding; status offline, last seen 30 days 3 hours ago.

Server details

Where does A Slice of Rust sit?

No region tag on A Slice of Rust. Where the machine stands is not checked here; Rust Metrics shows where the server says it is. Check: address. It reads 203.220.108.50:28015.

What Rust version is A Slice of Rust on?

Rust network protocol 2633 and build 165217 on Linux is the build A Slice of Rust runs. Check: protocol. To join, your game must match; Steam handles the update.

How reliable is A Slice of Rust, and is it online now?

Check: connection. A Slice of Rust is offline at this moment. Last contact was 30 days 3 hours ago. Reading: 0% uptime over the last 7 full days. It was up 0 of 168 hours. The first sighting on Rust Metrics was 28 September 2026.

Settings and map

What settings and rules apply on A Slice of Rust?

Check: gather rate. The name A Slice of Rust does not state one. No limit is set beyond the default. Groups take up to 8 players. The mode is survival. Note the following: the normal game: build, gather, raid. Check: PvP. Fighting and raiding between players are allowed. The server browser lists it under Community. Anti-cheat reading: VAC on, Valve's system.

What map is A Slice of Rust on?

Size 1,500 and seed 12345: the game generates the procedural map on A Slice of Rust from them. The map repeats when size and seed match. Open it on RustMaps from this page.

Connection

How do you connect to A Slice of Rust?

Check: join. Open Rust, press F1, then enter client.connect 203.220.108.50:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.

PLACARDS

Server tags

what each one means

Published as mp0,ptrak,$r?,v2633,gmrust,cs165217,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp0
Max players Slots: 0.
ts8
Group limit Default limit in force: 8 per team.
v2633
Protocol Your game must run protocol 2633 to get in.
cs165217
Build The server runs game build 165217.
ptrak
Networking Network layer: RakNet, the standard for the game.
$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.