It doesn't quite work like that, each service on the TCP or UDP protocols can use one or more ports, so for example, if you were hosting a webserver using HTTPS, that would, as standard be on port 443, so would be written as your IP address:443.
So your IP address does not use a port number per say, different services hosted from it will though and as you may realise this is also a way to host multiple services from a single IP. Now to expand on this a bit further, unless you are actually hosting any services yourself, then this isn't going to be much of a factor in anything as there are both local and remote ports. The specified port number, such as https on port 443 or http on port 80, FTP on 20 & 21 etc all refer to the remote port, the port that ends up being assigned locally when you connect as a client as a rule does not matter. Generally as a client (i.e. the consumer of the service) it wont matter much, unless you are setting up a default deny firewall ruleset for outbound connections at least.
If you are running a local media server on your home network, which could well be something you are doing, there will be a port specified for that, but the software you are using to run it will tell you what that is as you should be able to change it if you like.
I could give you some pointers on using netstat to look at local listening ports etc but to be honest I think that's beyond the scope here as I don't think you really quite understand what you are asking about here so that's probably not especially helpful to you. If you do have something specific in mind though by all means ask.
