#1
Offline 37.135.183.49:28015 checked 12d ago
Players
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 18d 12h. 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
- 160/ 200
- 195/ 225
- 93/ 200
- 111/ 200
- 75/ 100
- 91/ 300
Quick answers
Tags and filters
Where does #1 appear in Rust Going Deep lists and filters?
The Rust Going Deep lists that carry #1 are: Rust community servers, going deep. Its entry appears under the filters Type: Community (not modded, not official) and No plugins at all; Server tag: Monthly ^m; Group limit: 5 or more; Wipe schedule: Monthly.
How should you read the tags on #1?
gmvanilla (Game mode): It's vanilla survival; mp5 (Max players): There are 5 slots on this server; ts8 (Group limit): It uses the default team limit: 8; v2634 (Protocol): To join, your game has to be on protocol 2634; cs166652 (Build): It's on build 166652; ptrak (Networking): The network layer is RakNet, Rust's default; $r? (Region code): The region field is empty; ^m (Monthly): Monthly wipes, timed with the Facepunch force wipe — that is the tag list #1 puts out for the game's server browser. The tags carry its player count right now, its queue and the world's age, and all three are displayed up top.
Server info
What's the location of #1?
No region comes from #1. Rust Going Deep takes the server's word for its location and does not find out where the hardware sits. You can reach it at 37.135.183.49:28015.
What's the uptime like for #1?
Right now #1 is offline, having last been seen 12 days 3 hours ago. Over the past full 7 days it stayed up for 0 of 168 hours, or 0%. Rust Going Deep has had it on record since 5 October 2026.
What Rust version is #1 on?
Rust network protocol 2634 and build 166652 is what #1 runs, on Windows. The protocol must match to join; Steam will update your game.
Wipe info
What schedule does #1 follow for wipes?
The next wipe for #1 is an estimate based on the force wipe. When every Rust server wipes on Thursday 5 November at 19:00 UTC, that force wipe is its next wipe. The world you are on now was created 16 days 11 hours. The tags list wipes scheduled every month.
Rules and settings
What settings and rules have been applied to #1?
No gather rate appears in the name of #1. The group limit is the game's default of 8 players. It runs survival, gather, build and raid, the standard game. You can fight and raid other players. Community is where the server browser puts it, as a community server. The server runs Valve's anti-cheat, VAC.
What's the map on #1?
The map on #1 is procedural, made by the game.
Player stats
What's the population like on #1?
The last sighting of #1 was 12 days 3 hours ago; it is offline right now.
What's #1's rank among Rust servers?
For player hours in the last seven days, #1 ranks #13,782, within the top 61% of ranked servers.
Getting in
What's the way to join #1?
Open Rust and press F1, then type client.connect 37.135.183.49:28015. Alternatively, click Launch Rust on this page to join via Steam.