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

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

时间msgraw packet
2019-04-26 21:46:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:44:23!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-04-26 21:42:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 21:40:22!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-04-26 21:38:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:36:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:34:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:32:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:30:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:28:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:26:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:24:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:22:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:20:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:18:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 21:16:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:14:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:12:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:10:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:08:22!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-04-26 21:06:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:04:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 21:02:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 21:00:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:58:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:56:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:54:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:52:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:50:25!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:48:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:46:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:44:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:42:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:40:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:38:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:36:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:34:25!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:32:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:30:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:28:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:26:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:24:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:22:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:20:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:18:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:16:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:14:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:12:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:10:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:08:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:06:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:04:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 20:02:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 20:00:22!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-04-26 19:58:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:56:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:54:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:52:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:50:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 19:48:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:46:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:44:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 19:42:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:40:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:38:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:36:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:34:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:32:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:30:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:28:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:26:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:24:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 19:22:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:20:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:18:22!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-04-26 19:16:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:14:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:12:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:10:24!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:08:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:06:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 19:04:25!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 19:02:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 19:00:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:58:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:56:24!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:54:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:52:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 18:50:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:48:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:46:22!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-04-26 18:44:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:42:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:40:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:38:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:36:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:34:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:32:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:30:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:28:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:26:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:24:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:22:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:20:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:18:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 18:16:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 17:14:21!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-04-26 17:12:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 17:10:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 17:08:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 17:06:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 17:04:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 17:02:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 17:00:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:58:21!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-04-26 16:56:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:54:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:52:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:50:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:48:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:46:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:44:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:42:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:40:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:38:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:36:27!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:34:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:32:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:30:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 16:28:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:26:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:24:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:22:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 16:20:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:18:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:16:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:14:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:12:21!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-04-26 16:10:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 16:08:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:06:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:04:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 16:02:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 16:00:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:59:05!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:58:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:56:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:54:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:52:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:50:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:48:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:46:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:44:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:42:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:40:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:38:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:36:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:34:51!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:34:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:32:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:30:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:28:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:26:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:24:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:22:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:20:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:18:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:16:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:14:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:12:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:10:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:08:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:06:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:04:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 15:02:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 15:00:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:58:21!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-04-26 14:56:24!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:54:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:52:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:50:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:48:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 14:46:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 14:44:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:42:20!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-04-26 14:40:23!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:38:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:37:22!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:36:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:34:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:32:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 14:30:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:28:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:26:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:24:28!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:22:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:20:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:18:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:16:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 14:14:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:12:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 14:10:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:08:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 14:06:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:04:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:02:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 14:00:20!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-04-26 13:58:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:56:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:54:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:52:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:50:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:48:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:46:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:44:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:42:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:40:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:38:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:36:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:34:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:32:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:30:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:28:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:26:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:24:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:22:21!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-04-26 13:20:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:18:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:16:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:14:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 13:12:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 13:10:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:08:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:06:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:04:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 13:02:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 13:00:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:58:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:56:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:54:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:52:20!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-04-26 12:50:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:48:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:46:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:44:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:42:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:40:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:38:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:36:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:34:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:32:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:30:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:28:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:26:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:24:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:22:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:20:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:18:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:16:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:14:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:12:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:10:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:08:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 12:06:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:04:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 12:02:19!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-04-26 12:00:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:58:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:56:20!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-04-26 11:54:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:52:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:50:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:48:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:46:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:44:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:42:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:40:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:38:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:36:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:34:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:32:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:30:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:28:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:26:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:24:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:22:19!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-04-26 11:20:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:18:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:16:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:14:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:12:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:10:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:08:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:06:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:04:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 11:02:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 11:00:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:58:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 10:56:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:54:19!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-04-26 10:52:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:50:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:48:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:46:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:44:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:42:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 10:40:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:38:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 10:36:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:34:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:32:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:30:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:28:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:26:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:24:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:22:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 10:20:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:18:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:16:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:14:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:12:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 10:10:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:08:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:06:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:04:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:02:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 10:00:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:58:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:56:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:54:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:52:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:50:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:48:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:46:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:44:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:42:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:40:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:38:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:36:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:34:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:32:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 09:30:26!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:28:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:26:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:24:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:22:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 09:20:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:18:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:16:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:14:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:12:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 09:10:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 09:08:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:06:21!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:04:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:02:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 09:00:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:58:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:56:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:54:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 08:52:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:50:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 08:48:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:46:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:44:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:42:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:40:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:38:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:36:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 08:34:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:32:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:30:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:28:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 08:26:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:24:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:22:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:20:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:18:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:16:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 08:14:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:12:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:10:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:08:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:06:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:04:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:02:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 08:00:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:58:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:56:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:54:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:52:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:50:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:48:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:46:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:44:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:42:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:40:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:38:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:36:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:34:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:32:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:30:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:28:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:26:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:24:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:22:18!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-04-26 07:20:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:18:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:16:45!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 07:14:18!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-04-26 07:12:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:10:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:08:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:06:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:04:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:02:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 07:00:18!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-04-26 06:58:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:56:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:54:18!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-04-26 06:52:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 06:50:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:48:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:46:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:44:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 06:42:18!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-04-26 06:40:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:38:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 06:36:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:34:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:32:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:30:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:28:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:26:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:24:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:22:20!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:20:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:18:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:16:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:14:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:12:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:10:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:08:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:06:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:04:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:02:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 06:00:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:58:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 05:56:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 05:54:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:52:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 05:50:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 05:48:18!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-04-26 05:46:18!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-04-26 05:44:18!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-04-26 05:42:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:40:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:38:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:36:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:34:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 05:32:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:30:17!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-04-26 05:28:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:26:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 05:24:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:22:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:20:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:18:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 05:16:18!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:12:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:10:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:08:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:06:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:04:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:02:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 04:00:17!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-04-26 03:58:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:56:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:54:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:52:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:50:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:48:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:46:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:44:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:42:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:40:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:38:17!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-04-26 03:36:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:34:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:32:17!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-04-26 03:30:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:28:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:26:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:24:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:22:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:20:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:18:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:16:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:14:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:12:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:10:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:08:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:06:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:04:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 03:02:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 03:00:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:58:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:56:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:54:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:52:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:50:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:48:17!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-04-26 02:46:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:44:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:42:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:40:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:38:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:36:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:34:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:32:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:30:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:28:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:26:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:24:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:22:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:20:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:18:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:16:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:14:17!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-04-26 02:12:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:10:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:08:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:06:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:04:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 02:02:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 02:00:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:58:17!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-04-26 01:56:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:54:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 01:52:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:50:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:48:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:46:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:44:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:42:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:40:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 01:38:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 01:36:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:34:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 01:32:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:30:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:28:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:26:16!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-04-26 01:24:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:22:17!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:20:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:18:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:16:16!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-04-26 01:14:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:12:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:10:19!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:08:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:06:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:04:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:02:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 01:00:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:58:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:56:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:54:16!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-04-26 00:52:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:50:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:48:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:46:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:44:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:43:10!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:42:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:40:16!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-04-26 00:38:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:36:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:34:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:32:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:30:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:28:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:26:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:24:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:22:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:20:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:18:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:16:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:14:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:12:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:10:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:08:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:06:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:04:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V
2019-04-26 00:02:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.2V
2019-04-26 00:00:16!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3VBI4RZH-10>APET51,TCPIP*,qAC,T2HK:!3114.76N/12016.72ErPHG2330 WuXi.JS.China.Aprs.431.040Mhz 9.3V