US | 2x |DEVELOPEMENT|
Online 104.143.2.118:29015 checked 7m ago
Server instruments
last reading Thu 04:00 UTCPlayers now
0% full 7-day avg7-day peakServer fps
48 h low 25 · below 20 is lag, below 10 is badEntities
48 h range 65,773–74,234 · memory 1,839 MBUptime
15 h 54 min since its last restart, at the last readingPlayers
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, measured since 27 Sep. From asking the server directly; low fps and a climbing entity count mean lag.
Rank
daily · 1 is bestTop 43% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
too few wipes seen yetNot enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 0, 0 hours in.
Wipes
newest first| Wiped | Peak | Crowd | Lasted | Players before |
|---|---|---|---|---|
| Mon 12 Oct, 21:32 UTC16d ago | 0 | – | running | 0 |
| Sun 27 Sep, 06:17 UTC31d ago | 4 | halved by day 2 | 15.6 days | 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.
Similar servers
the same kind of game, then region, group limit, rate and wipes- 103/150
- 119/200
- 73/200
- 3/150
- 3/200
- 266/350
Quick answers
from the figures on this pageWipe timing
What happens on US | 2x |DEVELOPEMENT| when wipe day comes?
The busiest point of its recent wipes drew 2 players on average. 0 hours after the wipe, the crowd peaked on the latest wipe. The crowd stayed above half that peak until the next wipe in 0% of its recent wipes. When it didn't hold, by day 2 it fell below half.
When does US | 2x |DEVELOPEMENT| wipe?
To tell the rhythm of US | 2x |DEVELOPEMENT|, 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. 16 days 8 hours ago the current world was made.
Tags
How should you read the tags on US | 2x |DEVELOPEMENT|?
These are the tags US | 2x |DEVELOPEMENT| publishes, and the server browser reads them: gmrust (Game mode): The game mode is plain Rust survival; mp100 (Max players): 100 slots in total; ts8 (Group limit): Default limit in force: 8 per team; v2635 (Protocol): Your game must run protocol 2635 to get in; cs168909 (Build): Game build reading: 168909; ptrak (Networking): RakNet carries the traffic, as standard for Rust; $r? (Region code): The region field is empty; ^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.
Which lists and filters on Rust Metrics show US | 2x |DEVELOPEMENT|?
On Rust Metrics, US | 2x |DEVELOPEMENT| sits in these lists: 2x Rust servers, checked live, Modded Rust servers, checked live and North America: server readout. These filters bring it up on the server list: Region: North America; Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more; Gather rate: 2x.
Occupancy
What position does US | 2x |DEVELOPEMENT| hold among Rust servers?
Player hours over seven days put US | 2x |DEVELOPEMENT| at #9,664, in the top 43% of all ranked servers.
What player count does US | 2x |DEVELOPEMENT| carry?
Current headcount on US | 2x |DEVELOPEMENT|: 0 players, 100 slots available. Check: players over seven days. Average 0, peak 2.
Server
Where does US | 2x |DEVELOPEMENT| sit?
Reading: location. Nothing in the tags, but the name of US | 2x |DEVELOPEMENT| points to North America. Rust Metrics does not look up where the machine stands; it shows where the server says it is. Connect using 104.143.2.118:29015.
What Rust version is US | 2x |DEVELOPEMENT| on?
Version check: Rust network protocol 2635 and build 168909 on Windows, run by US | 2x |DEVELOPEMENT|. Check: protocol. To join, your game must match; Steam handles the update.
Is performance on US | 2x |DEVELOPEMENT| within range?
Over the last 48 hours the average was 25 server fps; the floor was 25. Check: entities. The peak was 74,234, counting buildings, deployables and the rest of the world. Memory peak: 2,014 MB. What players call lag comes from low fps and an entity count on the rise.
How reliable is US | 2x |DEVELOPEMENT|, and is it online now?
US | 2x |DEVELOPEMENT| reports online. Status: normal. Reading: uptime. About 15 hours ago it restarted, on its own count. Reading: 99% uptime over the last 7 full days. It was up 167 of 168 hours. Reading: first seen 27 September 2026, recorded by Rust Metrics.
Rules and settings
What settings and rules apply on US | 2x |DEVELOPEMENT|?
Gather rate check: 2x. That comes from the name US | 2x |DEVELOPEMENT|. 8 players per group, the default value. The mode is survival. Note the following: standard play of gathering, building and raiding. Check: PvP. Fighting and raiding between players are allowed. Plugins or settings change the game, so it is listed as Modded. Check: plugins. It runs Oxide of them. Check: anti-cheat. VAC, Valve's system, is on.
Which map is live on US | 2x |DEVELOPEMENT|?
Check: map. Procedural, size 3,750, seed 33333, generated by the game on US | 2x |DEVELOPEMENT|. Check: map view. Size and seed match, so the map is the same; view it on RustMaps from this page. Its map carries the name SCRAPLAND.GG.
Connection
How do you connect to US | 2x |DEVELOPEMENT|?
To join: start Rust, press F1 and type client.connect 104.143.2.118:29015. Or press Launch Rust here and Steam opens the game and connects you.