2 entries are registered on port 4950. It is a registered port (1024–49151) — IANA records an assignee, but nothing stops other software from listening here, which is why the number carries more than one entry.
services registered on this number
2 transports in use
entries encrypted on the wire
2 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :4950 | Cylon UC32 Control | TCPUDP | Network Services | caution | 5.8k |
| :4950 | Sybase Server Monitor | TCPUDP | Databases | safe | 0 |
Port 4950 is designated for Cylon Controls UC32 communication, primarily used in building automation systems for managing HVAC and lighting via control network communications. It facilitates real-time data exchange and command transmission between central controllers and distributed devices to maintain optimal building operations.
port 4950 as Cylon UC32 Control →Port 4950 is assigned to Sybase Server Monitor over TCP and UDP; no widely established deployment is known.
port 4950 as Sybase Server Monitor →The registry says what 4950 is registered to. What is listening on it right now is decided by the host, and only the host can be asked. Each of these prints the process behind the socket.
ss -ltnp | grep ':4950\b'lsof -nP -iTCP:4950 -sTCP:LISTENnetstat -ano | findstr :4950On Linux and Windows the process name comes back with the socket; on macOS lsof needs sudo to name a process that isn't yours. Match what it prints against the 2 entries above.
A port number is not a service. Anything may listen on 4950 — what you actually met is decided by the host, not the registry. If a service is missing here, it belongs in the registry.
contribute an entry