Offline 103.62.155.217:28500 checked 23d ago
chill-dev-test
Connect
srv = rust.server("103.62.155.217:28502")
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. 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 bestTop 71% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · no rhythm it keeps
srv.wipe_schedule()Its wipes keep no rhythm, so there is no next wipe to predict. 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, 10 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Sat 3 Oct, 12:29 UTC26d ago | 0 | NaN | running | 0 |
| 1 | Tue 22 Sep, 06:03 UTC37d ago | 1 | halved by day 5 | 11.3 days | 0 |
| 2 | Fri 18 Sep, 05:12 UTC41d ago | 0 | NaN | 4 days | 0 |
| 3 | Thu 10 Sep, 09:22 UTC49d ago | NaN | NaN | 7.8 days | 0 |
# 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 103.62.155.217:28500
- region
- –
- max players
- 1
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 3 Oct 2026, 12:29 UTC
- hostname
- –
- first seen
- 13 Sep 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 | ShockRust | Blue | NoLimit | no group limit · 149 on average | 21/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 132/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 121 on average | 36/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 96 on average | 10/700 |
| 4 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|СИБИРСКИЙ 27.10 | EU · groups of 16+ · monthly · 93 on average | 44/700 |
| 5 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 85 on average | 182/215 |
Quick answers
From the figures on this page.
Population
Against other Rust servers, how does chill-dev-test rank?
Over the last seven days chill-dev-test sits at #15,967 on player hours, in the top 71% of ranked servers.
How full does chill-dev-test run?
chill-dev-test returns no live count at this refresh, having last been seen 23 days 2 hours ago.
Server facts
Which Rust version is chill-dev-test on?
The build is Rust network protocol 2634 and build 166652 on Windows, run by chill-dev-test. Joining needs the same protocol on your game; Steam handles the update.
Is chill-dev-test up, and what does its uptime show?
The latest sample has chill-dev-test offline, with a last sighting 23 days 2 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. The first row Rust Data holds for it is dated 13 September 2026.
Where does chill-dev-test sit?
No region is published by chill-dev-test. Rust Data does not look up where the machine stands; it shows where a server says it is. You can reach it at 103.62.155.217:28500.
Rules, settings, map
What rules and settings are recorded for chill-dev-test?
No gather rate appears in the name: chill-dev-test. The group limit sits at the default of 8 players. survival is the game mode here, and the base game, where you gather, build and raid. Raids and player combat are enabled. It appears under Modded, where plugins or settings change how the game plays. Oxide plugins run on it. Anti-cheat status: VAC on.
Which map has chill-dev-test selected?
A procedural map runs on chill-dev-test, generated by the game.
Wipe data
When does chill-dev-test wipe, and on what schedule?
No next wipe can be predicted for chill-dev-test, which wipes at irregular times. Wipes are forced on all Rust servers once a month, and the next one is Thursday 5 November at 19:00 UTC. This world was created 26 days 12 hours ago.
What is wipe day on chill-dev-test like?
Recent wipes averaged 0 players at their peak. The crowd on the latest wipe topped out 10 hours after it began. Half the peak or more was held to the next wipe in 0% of recent wipes. In the wipes where it did not hold, half was lost by day 5.
Tags, lists
Which lists on Rust Data hold chill-dev-test, and which filters?
On Rust Data, chill-dev-test appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Oxide ^o; Group limit: 5 or more.
Which meanings do the tags on chill-dev-test hold?
Read by the game's server browser, the tags chill-dev-test publishes are: gmrust (Game mode): Survival play, standard Rust; mp1 (Max players): The server lists 1 slots; ts8 (Group limit): The default cap applies: 8 per team; v2634 (Protocol): Protocol 2634 is required; a different game version cannot connect; cs166652 (Build): Recorded game build: 166652; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): The region field is empty; ^o (Oxide): Runs on Oxide (uMod) for plugins; ^z (Modded): The Modded section lists it, because plugins or settings change the game. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Connecting
What is the way to join chill-dev-test?
In Rust, F1 opens the console: type client.connect 103.62.155.217:28500. Launch Rust on this page does the same by opening the game through Steam and connecting.