Online 160.251.203.118:28015 checked 7m ago
RustServer_4380
Connect
srv = rust.server("160.251.203.118:28017")
print(srv.connect_command)
Right now
srv.summary()
Players
srv.players.plot(range="48h")
Every five minutes, from the Steam server list.
Hourly average and peak, UTC.
Daily average and peak, UTC.
Server performance
srv.performance.plot(measure="fps", range="48h")
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.
Rank · daily · 1 is best
srv.rank.plot(invert=True) # 1 is best
Top 58% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule
srv.wipe_schedule()
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
Wipes · newest first
srv.wipes.head(20)
| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| Empty DataFrame · 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.
display(srv.map, srv.info())
Map
3000 · seed 10219
- map
- Procedural Map
- size
- 3000
- seed
- 10219
Server
srv.info()- address
- 160.251.203.118:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 10 Oct 2026, 23:50 UTC
- hostname
- –
- first seen
- 10 Oct 2026
Similar servers · the same kind of game, then region, group limit, rate and wipes
rust.similar(srv).head(6)
| server | like_this | players | |
|---|---|---|---|
| 0 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 472 on average | 70/250 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 320 on average | 93/200 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 283 on average | 199/250 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 279 on average | 4/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 265 on average | 244/250 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 259 on average | 380/375 |
Quick answers
From the figures on this page.
Player counts
How does RustServer_4380 compare in the rankings?
Player hours over seven days put RustServer_4380 at #12,975, in the top 58% of the ranked set.
What population does RustServer_4380 carry?
RustServer_4380 reports 0 players at this refresh, with 50 slots configured. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 06:00 UTC is the busiest, at 0 players.
About the server
How smoothly does RustServer_4380 run?
Averaged over 48 hours: 94 server fps, never under 68. The entity count peaked at 53,140, covering buildings, deployables and the rest of the world. A high of 2,567 MB of memory used. Lag, as players feel it, comes from an entity count that climbs and fps that falls.
Which Rust version is RustServer_4380 on?
Rust network protocol 2635 and build 168909 on Linux is what RustServer_4380 runs. Steam updates your game for you, but the protocol must match to join.
Is RustServer_4380 up, and what does its uptime show?
RustServer_4380 reports itself online at the current refresh. Count back 7 days 6 hours from its reported uptime to get the last restart. Over the last 7 full days the hours up number 167 of 168, 99%. Its earliest recorded date in Rust Data is 10 October 2026.
Which location does RustServer_4380 run from?
For RustServer_4380, no region is published. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 160.251.203.118:28015.
Map and rules
What rules and settings are recorded for RustServer_4380?
No gather rate appears in the name: RustServer_4380. The group limit sits at the default of 8 players. Game mode survival, with this note: gather, build, raid: the standard loop. Raids and player combat are enabled. The server browser lists it under Community. VAC is running: Valve's anti-cheat is on.
Which map has RustServer_4380 selected?
Size 3,000, seed 10219: the procedural map on RustServer_4380, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipe data
On what schedule does RustServer_4380 wipe?
Too few wipes are on record for RustServer_4380 to reveal its rhythm. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. The world it runs now was generated 19 days 5 hours ago.
Tags, lists
Which lists on Rust Data hold RustServer_4380, and which filters?
These Rust Data lists include RustServer_4380: Rust community servers, unfiltered. 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.
How should you read the server tags on RustServer_4380?
These tags are published by RustServer_4380 and read by the game's server browser: gmrust (Game mode): Survival play, standard Rust; mp50 (Max players): The server lists 50 slots; ts8 (Group limit): The default cap applies: 8 per team; v2635 (Protocol): Protocol 2635 is required; a different game version cannot connect; cs168909 (Build): Build number: 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): Region code: not set. At the top of this page you will also find the current players, the queue and the world creation time, all taken from the tags.
Join steps
What is the way to join RustServer_4380?
In Rust, F1 opens the console: type client.connect 160.251.203.118:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.