Not ranked yet, so there is no place in the school to report.
Uptimehours on the list, last 48
unmarked
–
Not seen long enough to take a register.
Performanceserver fps, last 48 hours
unmarked
–
Did not answer our direct query, so this subject went unmarked.
Wipeskeeping the crowd after a wipe
unmarked
–
Too few wipes seen to mark this yet.
Momentumrank now against a week ago
unmarked
–
No rank a week ago to compare with.
Not enough figures yet to write a report. Check back after a few days on the list.
How it is marked: each subject is out of 100 from the figures on this page (population is the 7-day average against the slots, standing is 100 less the top share, uptime the hours of the last 48 it was seen, performance its fps against 60, wipes the share of its wipes that kept half their crowd, momentum its rank against a week ago with 50 for no change). The grade is their average: 95 and over is an A+, 90 an A, 85 an A−, 80 a B+, 75 a B, 70 a B−, 65 a C+, 60 a C, 55 a C−, 45 a D, under 45 an F.
Progress through the term
Its players, its performance and its rank, hour by hour and day by day. Dashed red lines are its wipes.
Players
No five-minute samples in the last two hours.
Every five minutes, from the Steam server list.
No hourly history yet.
Hourly average and peak, UTC.
No daily history yet.
Daily average and peak, UTC.
Server performance
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 48 hours.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 30 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 60 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
This server has not answered a direct query in the last 90 days.
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
No rank history yet.
Attendance: the wipe record
1 wipe day in the last 16 weeks
MTWTFSS
·······
·······
·······
·······
·······
·······
·······
·······
······W
·······
·······
·······
·······
·······
·······
···
JulAugSepOct
W wiped that day F the force wipe · today. From the wipes in the table below.
Wipe schedule
too few wipes seen yet
Not enough wipes seen yet to tell when the next one is. Every server wipes at the monthly force wipe.
wipe-day peak1players, last three wipes
The first 48 hours of its last wipes
Players each hour, from the hour of the wipe. The latest peaked at 1, 0 hours in.
Wipes
newest first
Wiped
Peak
Crowd
Lasted
Players before
Sun 13 Sep, 15:31 UTC44d ago
1
–
running
1
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.
Similar servers
classmates: the same kind of game, then region, group limit, rate and wipes
In what location does EZKiwi (WIP) Solo only, custom map. sit?
You'll find no region listed by EZKiwi (WIP) Solo only, custom map.. Rust Server Score reports the location a server gives; it does not check where the machine actually is. You can connect at 116.90.75.194:28025.
Is EZKiwi (WIP) Solo only, custom map. up, and how steady is its uptime?
The server is down: EZKiwi (WIP) Solo only, custom map. is offline now, with the last sighting 44 days 13 hours ago. It was up 0% of the time over the last 7 full days, 0 of 168 hours. The first sighting by Rust Server Score was on 13 September 2026.
What Rust version is EZKiwi (WIP) Solo only, custom map. on?
The server EZKiwi (WIP) Solo only, custom map. is on Rust network protocol 2633 and build 162929 under Windows. To join, your game must use the same protocol; Steam handles the update.
Wipe cycle
On what schedule does EZKiwi (WIP) Solo only, custom map. reset?
EZKiwi (WIP) Solo only, custom map. has not had enough wipes recorded to reveal its rhythm. The monthly force wipe reaches every Rust server, and the next one lands on Thursday 5 November at 19:00 UTC. It has been running its current world for 44 days 13 hours.
What happens on EZKiwi (WIP) Solo only, custom map. when wipe day arrives?
Across its recent wipes, the busiest moments averaged 1 players. 0 hours after the latest wipe began, the crowd hit its peak.
Population
Where does EZKiwi (WIP) Solo only, custom map. place in the wider field of Rust servers?
In the top – of all ranked servers, EZKiwi (WIP) Solo only, custom map. sits at #13,072 for player hours over the last seven days.
How many players does EZKiwi (WIP) Solo only, custom map. usually have?
EZKiwi (WIP) Solo only, custom map. is offline at the moment; the last time it was seen was 44 days 13 hours ago.
Tags
What do EZKiwi (WIP) Solo only, custom map.'s tags stand for?
You'll see EZKiwi (WIP) Solo only, custom map. tagged with gmvanilla (Game mode): This is vanilla survival; mp20 (Max players): 20 slots are available; ts1 (Group limit): Teams cap out at 1; v2633 (Protocol): The game protocol is 2633, so your game must match that version to join; cs162929 (Build): This runs on build 162929; ptrak (Networking): This is RakNet: the network layer Rust normally uses; $r? (Region code): A region code is not set here; ^q (Premium): Rust's premium status is required to join; ^o (Oxide): Plugin framework: Oxide (uMod); ^z (Modded): Plugins or settings alter the game, so it sits under Modded in the browser, which picks them up from the server. At the top of the page you'll see the live player count, the queue and the world's age, taken from the tags.
Which lists and filters on Rust Server Score show EZKiwi (WIP) Solo only, custom map.?
Rust Server Score lists that include EZKiwi (WIP) Solo only, custom map.: Modded Rust servers, graded and Solo Rust servers, graded. It shows under the following filters on the server list: Type: Modded; Game mode: Premium; Server tag: Premium ^q, Modded ^z and Oxide ^o; Group limit: Solo.
Rules and settings
Which rules does EZKiwi (WIP) Solo only, custom map. enforce, and what are its settings?
Nothing in the name of EZKiwi (WIP) Solo only, custom map. states a gather rate. No teams are allowed: it is solo only. You get survival here, gather and build and raid: the standard game. You can raid other players and fight them. Plugins or settings change the game here, and the server browser lists it under Modded. Plugins on it number Oxide. Rust's premium status is required to join. The server runs Valve's anti-cheat, VAC.
Connecting
What is the way to join EZKiwi (WIP) Solo only, custom map.?
Enter client.connect 116.90.75.194:28025 in the console after pressing F1 in Rust. Or use Launch Rust on this page to open Rust through Steam and connect automatically. Rust's premium status is required to join.
Server tags
what each one means
Published asmp20,ptrak,$r?,v2633,gmvanilla,cs162929,^q,ts1,^o^z
Game
gmvanilla
Game modeThis is vanilla survival.
mp20
Max players20 slots are available.
ts1
Group limitTeams cap out at 1.
v2633
ProtocolThe game protocol is 2633, so your game must match that version to join.
cs162929
BuildThis runs on build 162929.
ptrak
NetworkingThis is RakNet: the network layer Rust normally uses.
$r?
Region codeA region code is not set here.
Mods and access
^q
PremiumRust's premium status is required to join.
^o
OxidePlugin framework: Oxide (uMod).
^z
ModdedPlugins or settings alter the game, so it sits under Modded.
Players now (cp), the queue (qp) and the wipe time (born) are in the tag string too; they change every few minutes and are shown at the top of the page. Flag meanings are Facepunch's.
Not enough figures yet to write a report. Check back after a few days on the list.