Give your CS2 server a life outside the server browser

In the in-game list, your server is a name, a ping and a player count. What actually makes players stay — the rules, the atmosphere, organised session times, the Discord community, the plugins — appears nowhere. That's what the Zlobby listing is for: a public page you write, with availability data you can't embellish.

Zlobby probes your server through the Source query protocol (A2S), the same one every tool in the Valve ecosystem uses. Availability and latency are measured; server name, current map and player counts remain values declared by your machine, labelled as such.

The probe queries your server's Source query port — 27015 by default. If your host separates game and query ports, enter the one that answers A2S requests: it's the same port classic monitoring sites use. A server behind DDoS protection must allow inbound A2S queries for its status to stay measurable.

The listing is created and managed from the operator console, and appears in the CS2 server directory.

A surf server that welcomes beginners and a sweaty retake server looking for regulars are not aiming at the same crowd. State the expected level, the chat language, the moderation policy and the hours when the server is actually populated — that's the number one question players ask, and your listing's population history answers it honestly.

Does your server have a team side too? Players who join you can find each other through find CS2 teammates and form stacks in a dedicated Lobby.

The listing is free, with no time limit. Weekly featuring, paid in credits, only changes your position in the directory — never the status data, which is measured the same way for everyone.