最新 今天 统计 地图 地球 设置 关于

今天收到的 BI4RZH-10 418 APRS数据包 下载轨迹 aprs.fi hamclub hellocq 本站 本站轨迹

时间msgraw packet
2019-08-22 14:54:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:52:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:50:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:48:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:46:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:44:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:42:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:40:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:38:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:36:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:34:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:32:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:30:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:28:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:26:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:24:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:22:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:20:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:18:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:16:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:14:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:12:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:10:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:08:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:06:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:04:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:02:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 14:00:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:58:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:56:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:54:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:52:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:50:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:48:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:46:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:44:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:42:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:40:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:38:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:36:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:34:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:32:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:30:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:28:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:26:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:24:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:22:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:20:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:18:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:16:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:14:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:12:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:10:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:08:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:06:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:04:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:02:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 13:00:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:58:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 12:56:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:54:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:52:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:50:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:48:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:46:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:44:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:42:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:40:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:38:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:36:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:34:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:32:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:30:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:28:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:26:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:24:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:22:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:20:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:18:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:16:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:14:39!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:12:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:10:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:08:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:06:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:04:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:02:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 12:00:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:58:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:56:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:54:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:52:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:50:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:48:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:46:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 11:44:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:42:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:40:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:38:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:36:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:34:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:32:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:30:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:28:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:26:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:24:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:22:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:20:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:18:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:16:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:14:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:12:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:10:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:08:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:06:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:04:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:02:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 11:00:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:58:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:56:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:54:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:52:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:50:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 10:48:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:46:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:44:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:42:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:40:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:38:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:36:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:34:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:32:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:30:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:28:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:26:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:24:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 10:22:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:20:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:18:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:17:52!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:16:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:14:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:12:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:10:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:08:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:06:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:04:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:02:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 10:00:36!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:58:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:56:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:54:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:52:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:50:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:48:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:46:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:44:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 09:42:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:40:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:38:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:36:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:34:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 09:32:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:30:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:28:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:26:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:24:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:22:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 09:20:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:18:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:16:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:14:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:12:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:10:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:08:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:06:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:04:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:02:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 09:00:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:58:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:56:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:54:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 08:52:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:50:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:48:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:46:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:44:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:42:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:40:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:38:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:36:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:34:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:32:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:30:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:28:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:26:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:24:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:22:37!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:20:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 08:18:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:16:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:14:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:12:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:10:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:08:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:04:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:02:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 08:00:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:58:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:56:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:54:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:52:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:50:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:48:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 07:46:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 07:44:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:42:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:40:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:38:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:36:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:34:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:32:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:30:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:28:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:26:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:24:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:22:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:20:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:18:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 07:16:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:14:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:12:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:10:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:08:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:06:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:04:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:02:35!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 07:00:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:58:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:56:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:54:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:52:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:50:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:48:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:46:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 06:44:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:42:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:40:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:38:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:36:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:34:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:32:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:30:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 06:28:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:26:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:24:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:22:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:20:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:18:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:16:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:14:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:12:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:10:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:08:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 06:06:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:04:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 06:02:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 06:00:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:58:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:56:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:54:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:52:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:50:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:48:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:46:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:44:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:42:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 05:40:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:38:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:36:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 05:34:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:32:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:30:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:28:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 04:26:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 04:24:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 04:22:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:20:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:18:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:16:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:14:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:12:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:10:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 04:08:34!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:06:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:04:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:02:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 04:00:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:58:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:56:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:54:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:52:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 03:50:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:48:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:46:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:44:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:42:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:40:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:38:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:36:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:34:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:32:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:30:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:28:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:26:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:24:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 03:22:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:20:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:18:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:16:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:14:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:12:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:10:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:08:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 03:06:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 03:04:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:02:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 03:00:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:58:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:56:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:54:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:52:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:50:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 02:48:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 02:46:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:44:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:42:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:40:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 02:38:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:36:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:34:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:32:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 02:30:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:28:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 02:26:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:24:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 02:22:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:20:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:18:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:16:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:14:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:12:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:10:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:08:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:06:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:04:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:02:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 02:00:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:58:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:56:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:54:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:52:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 01:50:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:48:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:46:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:44:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:42:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:40:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:38:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:36:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:34:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:32:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:30:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 01:28:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:26:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:24:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:22:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:20:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:18:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:16:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 01:14:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:12:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:10:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 01:08:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:06:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:04:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.1V
2019-08-22 01:02:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 01:00:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:58:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:56:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:54:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:52:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:50:33!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:48:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:46:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:44:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:42:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:40:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:38:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:36:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:34:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:32:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:30:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:28:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:26:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:24:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:22:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 00:20:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:18:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:16:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:14:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:12:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:10:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:08:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:06:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 00:04:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V
2019-08-22 00:02:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 8.9V
2019-08-22 00:00:32!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.0V