The IP addresses you cite are indeed private addresses and exist only within the scope of your router/LAN. To allow access from outside, you may want to consider a dynamic domain name - freemium services like https://www.noip.com/ provide this. They also give pointers to help with port forwarding issues.
I have set up several RPis with NoIP domain names across a variety of LANs from academic to private, US to Asia, and all worked eventually. The only real challenge came with a commercial ISP in Japan. I had to resort to tools such as Zenmap and https://github.com/kaklakariada/portmapper (on MacOSX) to wrangle the router into allowing external access to the usual ports (80, 8080 for web pages, 5900 for VNC, 22 for ssh).
NoIP's solution is to: (1) provide you with a domain name; (2) have you install a little daemon that runs on your RPi. This daemon periodically communicates its location to the NoIP hub, which then keeps the DNS up to date with that address.
There are likely other dynamic domain name alternative services out there. This one is free, but at the cost of having to regularly confirm, by hand, that you still want to keep using the DN and the service.