Here is the same tracert using the OP's IP that he has given 202.67.50.139 over a 768Kbps DSL connection
C:\Users\Shockwave>tracert 202.67.52.81

Tracing route to 202.67.52.81 over a maximum of 30 hops

1 4 ms 3 ms 2 ms 192.168.1.254
2 58 ms 49 ms 46 ms pppoe.casstel.net [24.121.56.2]
3 48 ms 45 ms 47 ms gw.casstel.net [24.121.56.1]
4 49 ms 53 ms 54 ms 67.221.222.49
5 49 ms 48 ms 49 ms gi1-8.mpd01.mci01.atlas.cogentco.com [38.112.3.9
]
6 49 ms 49 ms 48 ms te0-3-0-2.mpd22.mci01.atlas.cogentco.com [154.54
.30.165]
7 64 ms 63 ms 64 ms te0-0-0-5.ccr22.dfw01.atlas.cogentco.com [154.54
.5.157]
8 63 ms 64 ms 63 ms te0-2-0-2.ccr22.iah01.atlas.cogentco.com [154.54
.25.214]
9 100 ms 103 ms 99 ms te0-2-0-3.ccr22.lax01.atlas.cogentco.com [154.54
.45.2]
10 102 ms 100 ms 99 ms te8-3.ccr02.lax05.atlas.cogentco.com [154.54.29.
202]
11 93 ms 93 ms 93 ms 38.104.84.42
12 198 ms 198 ms 198 ms gi11-0-0.cr1.nrt1.asianetcom.net [202.147.61.170
]
13 200 ms 203 ms 200 ms gi1-0-0.gw1.nrt5.asianetcom.net [202.147.0.178]

14 198 ms 201 ms 199 ms squareco.asianetcom.net [203.192.149.210]
15 202 ms 203 ms 201 ms 61.195.56.129
16 199 ms 200 ms 198 ms 219.117.144.2
17 204 ms 206 ms 205 ms 219.117.146.149
18 199 ms 199 ms 198 ms 219.117.146.129
19 210 ms 203 ms 206 ms 219.117.146.38
20 206 ms 204 ms 205 ms 202.67.52.81

Milliseconds - Average of 205 so that converts to 0.20500000000000002 seconds (Source http://www.convertunits.com/from/millisecond/to/seconds)

Which to me shows me that my frame rate is (unless my math is off) between 00:16:35:00 - 00:16:39:00 FPS

Which means that there is one huge Latency delay (16-17 frames)

In the OP's case his first tracert averaged at 210 (220ms + 211ms +199ms /3) so the conversion would be 0.21 seconds which then converts to in FPS = 00:16:40:00

The OP's second tracert averaged at again at 210 (210ms + 208ms + 212ms /3) so the conversion would be 0.21 seconds which then converts to in FPS once again at = 00:16:40:00

Sorry about the math (it give me a headache too)