RUST METRICSFlight deck · live data
Data live Servers11,597 Players47,678 Populated3,062 Fresh wipes 3 h111 Scan5 min
‹ All servers160.251.203.118:28015
Online Full Queue Fresh wipe Wipe due No query

RustServer_4380

Online 160.251.203.118:28015 checked 8m ago

COM 1 · connect

Server instruments

last reading Fri 06:00 UTC
0 12 25 38 50 PAX 0 /50

Players now

0% full 7-day avg7-day peak
0 10 30 60 120 256 FPS 97 SERVER FPS

Server fps

48 h low 68 · below 20 is lag, below 10 is bad
0 20 40 60 80 ENT 52,755 ×1000

Entities

48 h range 50,677–53,140 · memory 2,642 MB
1239 ET SINCE RESTART 7D 08H

Uptime

7 days 8 hours since its last restart, at the last reading
7-day average0peak 1
Rank#13,534top 61%
Last wipe19d agono schedule published
Next wipe–no wipe seen yet
Memory2,642MB48 h peak 1 players
REC 1

Players

AveragePeak
00.250.50.75108:0017:0003:0012:0021:0006:00

Hourly average and peak, UTC.

REC 2

Server performance

05010015020008:0017:0003:0012:0021:0006:00

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 11 Oct. From asking the server directly; low fps and a climbing entity count mean lag.

REC 3

Rank

daily · 1 is best
RankRank in region
15k10k15k20k11 Oct15 Oct19 Oct22 Oct26 Oct30 Oct

Top 61% 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 schedule

What wipe timing does RustServer_4380 follow?

Its rhythm cannot be told from the wipes of RustServer_4380 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. The world in play was created 19 days 7 hours ago.

Tag meanings

Which tags does RustServer_4380 carry, and what do they mean?

Check: tags. The game's server browser reads gmrust (Game mode): The game mode is plain Rust survival; mp50 (Max players): 50 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Protocol 2635: join only on the same game version; cs168909 (Build): Build 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty from RustServer_4380. 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 RustServer_4380?

Rust Metrics lists featuring RustServer_4380: 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 RustServer_4380 hold among Rust servers?

Ranking for RustServer_4380: #13,534 on seven-day player hours, top 61% of all ranked servers.

What is the population on RustServer_4380?

0 of 50 slots are filled on RustServer_4380 right now. Check: players over seven days. Average 0, peak 1. Check: 48-hour peak. 06:00 UTC, 0 players on average.

Server

What location is RustServer_4380 hosted in?

No region comes from RustServer_4380. Note: Rust Metrics shows the location a server gives, not where the machine stands. The endpoint you need is 160.251.203.118:28015.

What Rust version is RustServer_4380 on?

Reading: RustServer_4380, Rust network protocol 2635 and build 168909, Linux. Matching protocol is required to join. Let Steam update your game.

How does RustServer_4380 perform?

Reading: 94 server fps on average across the last 48 hours. It never dropped below 68. Peak entity count: 53,140. Buildings, deployables and all else included. Memory peak: 2,642 MB. Lag, as players feel it, is low fps plus a climbing entity count.

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

Reading: online. RustServer_4380 answers right now. Reading: uptime. About 7 days 8 hours ago it restarted, on its own count. Uptime for the last 7 full days: 167 of 168 hours, or 99%. The first sighting on Rust Metrics was 10 October 2026.

Settings and map

What settings and rules apply on RustServer_4380?

No gather rate appears in the name: RustServer_4380. 8 players per group, the default value. The mode is survival. Note the following: 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.

What map is RustServer_4380 on?

Check: map. Procedural, size 3,000, seed 10219, generated by the game on RustServer_4380. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page.

How to join

How do you connect to RustServer_4380?

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

PLACARDS

Server tags

what each one means

Published as mp50,ptrak,$r?,v2635,gmrust,cs168909,ts8

Game

gmrust
Game mode The game mode is plain Rust survival.
mp50
Max players 50 slots in total.
ts8
Group limit Default limit in force: 8 per team.
v2635
Protocol Protocol 2635: join only on the same game version.
cs168909
Build Build 168909.
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.