Offline 203.16.163.90:25976 checked 22d ago
VibeCoded Server!
Connect
srv = rust.server("203.16.163.90:25977")
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 17 Sep. 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 · too few wipes seen yet
srv.wipe_schedule()Not 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 1, 2 hours in.
Wipes · newest first
srv.wipes.head(20)| wiped | peak | crowd | lasted | players_before | |
|---|---|---|---|---|---|
| 0 | Fri 2 Oct, 11:03 UTC27d ago | 1 | NaN | running | 0 |
| 1 | Thu 17 Sep, 20:26 UTC41d ago | 1 | halved by day 3 | 14.6 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
1000 · seed 734127336
- map
- Procedural Map
- size
- 1000
- seed
- 734127336
Server
srv.info()- address
- 203.16.163.90:25976
- region
- –
- max players
- 10
- group limit
- 8, the default
- wipe schedule
- –
- last wipe
- 2 Oct 2026, 11:03 UTC
- hostname
- –
- first seen
- 14 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 | Rusty Moose |EU Mondays| | EU · groups of 12+ · weekly · 514 on average | 538/575 |
| 1 | Rustoria.co - EU East Long | EU · groups of 12+ · monthly · 318 on average | 430/475 |
| 2 | Rusty Moose |EU Main| | EU · groups of 12+ · weekly · 290 on average | 167/250 |
| 3 | Rustafied.com - EU Friday | EU · groups of 16+ · weekly · 275 on average | 57/100 |
| 4 | Rustoria.co - EU Main | EU · groups of 16+ · weekly · 275 on average | 221/250 |
| 5 | Rustoria.co - EU East Medium | EU · groups of 12+ · biweekly · 236 on average | 304/350 |
Quick answers
From the figures on this page.
Population data
Against other Rust servers, how does VibeCoded Server! rank?
Over the last seven days VibeCoded Server! sits at #15,956 on player hours, in the top 71% of ranked servers.
What population does VibeCoded Server! carry?
The current row shows VibeCoded Server! offline; the last response was 22 days 9 hours ago.
Server data
What Rust version does VibeCoded Server! run?
The build is Rust network protocol 2634 and build 166601 on Linux, run by VibeCoded Server!. Steam updates your game for you, but the protocol must match to join.
How reliable is VibeCoded Server!, and is it online now?
VibeCoded Server! is offline at this refresh; the last response came 22 days 9 hours ago. Over the last 7 full days the hours up number 0 of 168, 0%. Its earliest recorded date in Rust Data is 14 September 2026.
Where does VibeCoded Server! sit?
No region is published by VibeCoded Server!. The location shown by Rust Data is what a server says, not a lookup of where the machine stands. You can reach it at 203.16.163.90:25976.
Settings and map
Which rules apply on VibeCoded Server!, and what settings?
The name VibeCoded Server! carries no gather rate. The group limit sits at the default of 8 players. survival is the game mode here, and gather, build, raid: the standard loop. Fighting and raiding between players are allowed. The server browser lists it under Community. The VAC field reads off.
Which map has VibeCoded Server! loaded?
VibeCoded Server! runs a procedural map of size 1,000 with seed 734127336, generated by the game. Because size and seed determine the map, it can be viewed on RustMaps via this page.
Wipes and dates
When does VibeCoded Server! wipe, and on what schedule?
A rhythm cannot be read from the wipes of VibeCoded Server! on record, which are too few. The monthly force wipe applies to every Rust server, including this one; the next falls on Thursday 5 November at 19:00 UTC. The world it runs now was generated 27 days 3 hours ago.
On VibeCoded Server!, what happens on wipe day?
Across recent wipes the busiest point averaged 1 players. 2 hours after the latest wipe, the crowd reached its peak. Half the peak or more was held to the next wipe in 0% of recent wipes. The drop under half arrived by day 3 in the other cases.
Tags and filters
Where does VibeCoded Server! appear among Rust Data lists and filters?
On Rust Data, VibeCoded Server! appears in these lists: 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 VibeCoded Server!?
Read by the game's server browser, the tags VibeCoded Server! publishes are: gmrust (Game mode): Survival play, standard Rust; mp10 (Max players): Slot count: 10; ts8 (Group limit): Team limit of 8, as shipped by default; v2634 (Protocol): The server speaks protocol 2634, so match your game version; cs166601 (Build): Recorded game build: 166601; ptrak (Networking): Network traffic runs over RakNet, the game standard; $r? (Region code): No region code is set. Current players, queue length and world creation time are among the tags and are displayed at the top of this page.
Join steps
How can I connect to VibeCoded Server!?
In Rust, F1 opens the console: type client.connect 203.16.163.90:25976. Launch Rust on this page does the same by opening the game through Steam and connecting.