#1
Offline 37.135.183.49:28015 checked 22d ago
Server instruments
no direct query in 48 hoursPlayers now
20% full 7-day avgServer fps
no direct query answered in 48 hoursEntities
no direct query answered in 48 hoursUptime
no direct query answered in 48 hoursPlayers
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
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.
Rank
daily · 1 is bestTop 61% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
Next wipe Thursday 5 November, 19:00 UTC, in 7d 16h. The force wipe
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 120/200
- 86/200
- 31/350
- 83/400
- 143/200
- 56/100
Quick answers
from the figures on this pageWipe timing
What wipe timing does #1 follow?
The estimate for #1's next wipe comes from the force wipe. Force wipe falls on Thursday 5 November at 19:00 UTC. Every Rust server wipes then; yours included. The world in play was created 27 days 7 hours ago. A monthly wipe schedule is published in its tags.
Tags
Which tags does #1 carry, and what do they mean?
Check: tags. The game's server browser reads gmvanilla (Game mode): Survival on vanilla settings; mp5 (Max players): 5 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2634 (Protocol): Match the game version: protocol 2634 is required; cs166652 (Build): Build 166652; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): Region code: none set; ^m (Monthly): Facepunch's force wipe sets the monthly cycle here from #1. 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 #1?
These Rust Metrics lists carry #1: 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; Server tag: Monthly ^m; Group limit: 5 or more; Wipe schedule: Monthly.
Population
What position does #1 hold among Rust servers?
Ranking for #1: #13,782 on seven-day player hours, top 61% of all ranked servers.
What is the population on #1?
Reading for #1: offline at this moment; last seen 22 days 22 hours ago.
Server
Which location does #1 run from?
No region comes from #1. Note: Rust Metrics shows the location a server gives, not where the machine stands. Check: address. It reads 37.135.183.49:28015.
What Rust version is #1 on?
Reading: #1, Rust network protocol 2634 and build 166652, Windows. To get in, your game needs the same protocol; Steam applies the update.
Is #1 up, and how often does it stay up?
#1 reports offline. The last reading came 22 days 22 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 5 October 2026.
Map and rules
How is #1 configured, and what rules are in force?
Check: gather rate. The name #1 does not state one. 8 players per group, the default value. survival, the normal game: build, gather, raid — that is the game mode. Players can raid each other and fight. That is permitted here. Listing: Community server. VAC is on. That is Valve's anti-cheat.
Which map is live on #1?
The game generates a procedural map for #1.
How to join
How do you connect to #1?
Check: join. Open Rust, press F1, then enter client.connect 37.135.183.49:28015. Alternatively, use Launch Rust on this page: Steam opens Rust and connects you.