No registration exists; a listener here is typically a Windows RPC service, and the port number is not stable.
49167 is Dynamic/Private space under RFC 6335, so no service name is or can be attached to it. Windows Server assigns RPC endpoints from 49152-65535 in the order services start, meaning the exact number is an artifact of boot ordering rather than a property of the service. That is why the honest answer to "what is on 49167" is always a query to the endpoint mapper on TCP 135 or a look at the local process table, never a lookup table.
Do not expose
Do not publish dynamic RPC ports; if remote administration is needed, front it with a VPN rather than opening the range.
$ sudo lsof -nP -iTCP:49167 -sTCP:LISTENSeen this on your network? Beige Box scans your Wi-Fi and shows every open port on every device — and its Ports tool links straight back here.
Get Beige Box →also available as JSON · Markdown
Corrections or a missing port? Reply @rimrocksystems.