The only requirements is that both server and client agree on a port for the server.
You should definitely stay away from often used service ports for the simple reason that the server application will not be able to run
IF that port is already in use. This will not be very likely with port 828, it is a rarely used port and thus relatively safe to use.
If you use a well-known port for your custom server, you will have two possible problems:
(1) The server will fail to start because of conflicts (see above).
(2) You'll get stray traffic that your server will not understand, especially if you are not behind a firewall and use a port that is often exploited. For example
Dshield.org has reports on port scanning activity for each port number. You should definitely stay away from e.g. port 135, but many ports >1024 are also favorite targets. (OTOH, You can also see that 824 is very quiet.)
To see what server ports are in use on your machine, you can do a "netstat -an" (windows), look for lines ending in "listening".