Online 118.68.62.40:28015 checked 11m ago
TEST SERVER
Connect
srv = rust.server("118.68.62.40: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. 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 45% 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
- map
- Procedural Map
- size
- –
- seed
- –
Server
srv.info()- address
- 118.68.62.40:28015
- region
- –
- max players
- 50
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 24 Oct 2026, 16:05 UTC
- hostname
- –
- first seen
- 26 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 | ShockRust | Blue | NoLimit | no group limit · 150 on average | 105/500 |
| 1 | МИНИ-КАРТА 2Х | STORM | FPS+ 28.10 | EU · groups of 8+ · weekly · 128 on average | 123/100 |
| 2 | RETRO RUST #1 Х1000|NOLIMIT|LOOT++|KIT WIPE 27.10 | EU · groups of 16+ · weekly · 118 on average | 136/225 |
| 3 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|EU MAIN 25.10 | EU · groups of 16+ · monthly · 93 on average | 47/700 |
| 4 | RustSpain.com | EU Main | EU · groups of 12+ · weekly · 88 on average | 4/200 |
| 5 | 404 RUST 2Х|ДЛЯ НОВИЧКОВ|РУССКИЙ 24.10 | EU · groups of 16+ · monthly · 84 on average | 19/1000 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does TEST SERVER rank?
Rank #10,029 on seven-day player hours for TEST SERVER, within the top 45% of all ranked servers.
How full does TEST SERVER run?
Current row: 0 players on TEST SERVER, against 50 slots. Over the last seven days it averaged 0 players and peaked at 1. Averaged by hour over 48 hours, 12:00 UTC is the busiest, at 1 players.
Server data
What is the Rust version on TEST SERVER?
The build is Rust network protocol 2635 and build 168909 on Windows, run by TEST SERVER. The protocol has to match before you can join, and Steam does the updating.
How reliable is TEST SERVER, and is it up?
TEST SERVER reports itself online at the current refresh. Uptime of 90% across the last 2 full days: 43 hours of 48. Its earliest recorded date in Rust Data is 26 October 2026.
Where does TEST SERVER sit?
No region is published by TEST SERVER. Rust Data does not look up where the machine stands; it shows where a server says it is. 118.68.62.40:28015 is its address.
Map and rules
What rules and settings are recorded for TEST SERVER?
You will not find a gather rate in the string TEST SERVER. No custom cap; the default of 8 players per group stands. Game mode survival, with this note: 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. The plugin count is Carbon. VAC, Valve's anti-cheat, is enabled.
Which map has TEST SERVER selected?
TEST SERVER runs a procedural map, which the game generates.
Wipes and dates
On what schedule does TEST SERVER wipe?
Too few wipes are on record for TEST SERVER 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 4 days 16 hours ago.
Lists and tags
Where does TEST SERVER appear among Rust Data lists and filters?
On Rust Data, TEST SERVER appears in these lists: Modded Rust servers. It appears under these filters on the server list: Type: Modded; Server tag: Modded ^z and Carbon ^y; Group limit: 5 or more; Last wipe: In the last week.
How should you read the server tags on TEST SERVER?
These tags are published by TEST SERVER 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): Team limit of 8, as shipped by default; v2635 (Protocol): The server speaks protocol 2635, so match your game version; cs168909 (Build): The server runs build 168909; ptrak (Networking): The network layer is RakNet, standard for the game; $r? (Region code): No region code is set; ^z (Modded): The Modded section lists it, because plugins or settings change the game; ^y (Carbon): The plugin framework in use is Carbon. The tags also hold the current player count, the queue and when the world was made; these appear at the top of this page.
Join steps
What is the way to join TEST SERVER?
In Rust, F1 opens the console: type client.connect 118.68.62.40:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.