Online 27.45.44.6:28015 checked 9m ago
『微光』PVE|原倍|事件活动|萌新养老
Connect
srv = rust.server("27.45.44.6: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 34% of all ranked servers. Ranked on player hours over the last seven days.
Wipe schedule · from its schedule tag
srv.wipe_schedule()Next wipe Thursday 5 November, 19:00 UTC, in 8d 12h. # The force wipe · high confidence
Coming wipes
| in | at | kind | |
|---|---|---|---|
| 0 | 8d 12h | Thu 5 Nov, 19:00 UTC | FW force wipe |
| 1 | 13d 16h | Tue 10 Nov, 22:43 UTC | wipe |
| 2 | 27d 16h | Tue 24 Nov, 22:43 UTC | wipe |
| 3 | 36d 12h | Thu 3 Dec, 19:00 UTC | FW force wipe |
| 4 | 41d 16h | Tue 8 Dec, 22:43 UTC | wipe |
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Tue 27 Oct, 22:43 UTC7h ago | NaN | NaN | running | 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
- 27.45.44.6:28015
- region
- –
- max players
- 100
- group limit
- 8, the default
- wipe schedule
- biweekly
- last wipe
- 27 Oct 2026, 22:43 UTC
- hostname
- –
- first seen
- 27 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 | ［JP］初心者PVPサーバー｜RaidTime・ Events | EA · groups of 10+ · biweekly · 19 on average | 2/100 |
| 1 | [JP] RUST SOLO ONLY | PvP | Beginner [ L.R.S. ] 10/16~10/29 | EA · no group limit · biweekly · 4 on average | 2/20 |
| 2 | 瞌睡熊『5倍10废|10.28|萌新首选|无权限』 | EA · groups of 8+ · biweekly · 4 on average | 4/100 |
| 3 | [JP/PvE][BPリサーチ]MatoyServer初しん者〇 | EA · groups of 8+ · biweekly · 2 on average | 1/50 |
| 4 | [JPN] Apple Server | PvP | Vanilla | 2Weekly | EA · groups of 8+ · biweekly · 2 on average | 4/50 |
| 5 | cczsbwd/solo/独狼/原倍半月清/月图/公益服 | EA · no group limit · biweekly · 1 on average | 3/50 |
Quick answers
From the figures on this page.
Player counts
Against other Rust servers, how does 『微光』PVE|原倍|事件活动|萌新养老 rank?
Over the last seven days 『微光』PVE|原倍|事件活动|萌新养老 sits at #7,495 on player hours, in the top 34% of ranked servers.
How many players does 『微光』PVE|原倍|事件活动|萌新养老 hold at once?
The sample now reads 0 players for 『微光』PVE|原倍|事件活动|萌新养老, out of 100 slots. Over the last seven days it averaged 0 players and peaked at 1. The 48-hour sample puts the busiest hour at 06:00 UTC, averaging 1 players.
Server data
Which Rust version is 『微光』PVE|原倍|事件活动|萌新养老 on?
Version Rust network protocol 2635 and build 168909 on Windows is reported by 『微光』PVE|原倍|事件活动|萌新养老. Steam updates your game for you, but the protocol must match to join.
How reliable is 『微光』PVE|原倍|事件活动|萌新养老, and is it up?
The current sample puts 『微光』PVE|原倍|事件活动|萌新养老 online. The first row Rust Data holds for it is dated 27 October 2026.
Where does 『微光』PVE|原倍|事件活动|萌新养老 sit?
The name of 『微光』PVE|原倍|事件活动|萌新养老 points to Asia, even though no region tag 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 27.45.44.6:28015.
Settings and map
What rules and settings are recorded for 『微光』PVE|原倍|事件活动|萌新养老?
The name 『微光』PVE|原倍|事件活动|萌新养老 carries no gather rate. 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. Browser listing: Modded. Plugins or settings modify the game. Oxide plugins run on it. Anti-cheat status: VAC off.
What is the map on 『微光』PVE|原倍|事件活动|萌新养老?
The game generates its map: procedural, on 『微光』PVE|原倍|事件活动|萌新养老.
Wipes and dates
When does 『微光』PVE|原倍|事件活动|萌新养老 wipe, and how often?
Too few wipes are on record for 『微光』PVE|原倍|事件活动|萌新养老 to confirm its schedule, so the tag drives the prediction. Every Rust server wipes at the force wipe on Thursday 5 November at 19:00 UTC, which is its next wipe. This world was created 7 hours ago. The tags list a two-weekly wipe cycle.
Tags and filters
Which lists on Rust Data hold 『微光』PVE|原倍|事件活动|萌新养老, and which filters?
The Rust Data lists that 『微光』PVE|原倍|事件活动|萌新养老 fits are: Modded Rust servers. These filters bring it up on the server list: Region: Asia; Type: Modded; Server tag: Biweekly ^b, Modded ^z and Oxide ^o; Group limit: 5 or more; Wipe schedule: Every two weeks; Last wipe: In the last 24 hours.
How should you read the server tags on 『微光』PVE|原倍|事件活动|萌新养老?
These tags are published by 『微光』PVE|原倍|事件活动|萌新养老 and read by the game's server browser: gmrust (Game mode): Rust survival in its standard form; mp100 (Max players): Slot count: 100; 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): Recorded game build: 168909; ptrak (Networking): Standard network layer for Rust: RakNet; $r? (Region code): Region code: not set; ^b (Biweekly): Wipes run on a two-week cycle; ^o (Oxide): The plugin framework in use is Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded. 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.
Connecting
How can I connect to 『微光』PVE|原倍|事件活动|萌新养老?
In Rust, F1 opens the console: type client.connect 27.45.44.6:28015. Launch Rust on this page does the same by opening the game through Steam and connecting.