RUST METRICSFlight deck · live data
Data live Servers11,655 Players43,200 Populated2,897 Fresh wipes 3 h105 Scan5 min
‹ All servers49.64.99.35:28015
Offline Full Queue Fresh wipe Wipe due No query

3537

Offline 49.64.99.35:28015 checked 3d ago

moddedoxide
COM 1 · connect

Server instruments

no direct query in 48 hours
0 125 250 375 500 PAX 1 /500

Players now

0% full 7-day avg7-day peak
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 average1peak 1
Rank#7,662top 34%
Last wipe3d agono schedule published
Next wipe–too few wipes 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
12.5k5k7.5k10k25 Oct26 Oct27 Oct28 Oct29 Oct30 Oct

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

PLAN

Wipe schedule

too few wipes seen yet

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

wipe-day peak1players, last three wipes

The first 48 hours of its last wipes

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
Mon 26 Oct, 08:41 UTC3d ago 1 – running 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

Wipe timing

What should you expect from wipe day on 3537?

The busiest point of its recent wipes drew 1 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe.

What wipe timing does 3537 follow?

To tell the rhythm of 3537, too few of its wipes are on record. 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 3 days 19 hours ago.

Tag meanings

How should you read the tags on 3537?

Tags published by 3537, read by the game's server browser: gmrust (Game mode): The game mode is plain Rust survival; mp500 (Max players): The server holds 500 slots; 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): Region code: none set; ^o (Oxide): Check: framework. Oxide (uMod) handles plugins; ^z (Modded): Plugins or settings make this a modded server. Players now, queue and world creation time sit in the tags as well, and appear at the top of this page.

Where does 3537 appear in Rust Metrics lists and filters?

Rust Metrics lists featuring 3537: Modded Rust servers, checked live. These filters bring it up on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Last wipe: In the last week.

Occupancy

What position does 3537 hold among Rust servers?

Ranking for 3537: #7,662 on seven-day player hours, top 34% of all ranked servers.

How full does 3537 get?

3537 is not responding; status offline, last seen 3 days 16 hours ago. Check: players over seven days. Average 1, peak 1.

Server details

Which location does 3537 run from?

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

What Rust version is 3537 on?

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

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

Check: connection. 3537 is offline at this moment. Last contact was 3 days 16 hours ago. Uptime for the last 4 full days: 7 of 96 hours, or 7%. Reading: first seen 25 October 2026, recorded by Rust Metrics.

Settings and map

What rules does 3537 enforce, and what are its settings?

Reading the name gives no gather rate for 3537. 8 players per group, the default value. The mode is survival. Note the following: 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 as Modded, where plugins or settings change how the game plays. Oxide plugins are running. VAC is on. That is Valve's anti-cheat.

Which map is live on 3537?

The game generates a procedural map for 3537.

Join

What do you do to join 3537?

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

PLACARDS

Server tags

what each one means

Published as mp500,ptrak,$r?,v2635,gmrust,cs168909,ts8,^o^z

Game

gmrust
Game mode The game mode is plain Rust survival.
mp500
Max players The server holds 500 slots.
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 Region code: none set.

Mods and access

^o
Oxide Check: framework. Oxide (uMod) handles plugins.
^z
Modded Plugins or settings make this a modded server.

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.