2 entries are registered on port 5313. 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
1 of 2 iana-registered
| port | service | proto | category | risk | views |
|---|---|---|---|---|---|
| :5313 | Ginever.net Communication | TCPUDP | Network Services | caution | 7.3k |
| :5313 | Real-time & Reliable Data | TCPUDP | — | safe | 0 |
Port 5313 is used primarily by Ginever.net to facilitate real-time data communication between servers and client applications, such as multiplayer gaming services, chat functions, or data synchronization. Its versatile support for TCP and UDP allows it to balance reliability with speed in data transfer, making it suitable for interactive network services within the Ginever.net ecosystem.
port 5313 as Ginever.net Communication →Port 5313 is assigned to Real-time & Reliable Data, a little-known service registered to Ted Hoshi.
port 5313 as Real-time & Reliable Data →The registry says what 5313 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 ':5313\b'lsof -nP -iTCP:5313 -sTCP:LISTENnetstat -ano | findstr :5313On 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 5313 — 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