今天收到的 BG4IOK-10 220 APRS数据包 下载轨迹 aprs.fi hamclub 本站
时间 | msg | raw packet |
---|---|---|
2025-06-01 19:04:33 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:59:36 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:54:35 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:49:34 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:44:37 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:39:36 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:29:39 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:24:37 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:20:26 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:15:25 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:10:23 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:05:22 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 18:00:25 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:55:24 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:50:23 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:45:26 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:40:24 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:35:28 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:30:26 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:25:25 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:20:28 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:15:26 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:10:30 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:05:28 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 17:01:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:56:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:51:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:46:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:41:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:36:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:31:13 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:26:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:21:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:16:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:11:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:06:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 16:01:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:56:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:51:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:46:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:41:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:36:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:31:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:26:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:21:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:16:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:11:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:06:23 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 15:01:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:56:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:51:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:46:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:41:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:31:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2FZ:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:26:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2FZ:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:21:21 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2FZ:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:16:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:11:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:06:21 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 14:01:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:56:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:51:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:46:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:41:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:36:22 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:31:21 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:26:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:22:03 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:17:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:12:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:07:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 13:02:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:57:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:52:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:47:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:42:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:37:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:32:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:27:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:22:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:17:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:12:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:07:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 12:02:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:57:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:52:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:47:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:42:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:37:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:32:11 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:27:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:22:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:17:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:12:11 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:07:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 11:02:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:57:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:52:11 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:42:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:32:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:22:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:12:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 10:02:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2HK:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:37:13 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:32:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:27:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:22:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:17:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:12:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:07:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 09:02:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:57:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:52:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:47:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:42:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:37:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:32:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:27:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:22:21 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:17:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:12:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:07:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 08:02:21 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:57:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:52:19 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:47:23 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:42:22 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:37:21 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:32:24 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:27:23 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:22:22 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:17:22 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:12:26 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:08:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 07:03:54 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:58:53 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:53:52 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:48:56 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:43:55 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:38:54 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:33:53 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:28:57 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:23:56 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:18:55 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:13:54 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:08:58 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 06:03:57 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:58:56 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:53:55 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:48:59 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:43:59 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:38:58 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:33:57 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:29:01 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:24:00 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:18:59 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:13:58 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:09:03 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 05:04:02 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:59:00 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:54:00 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:49:03 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:44:02 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:39:01 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:34:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:29:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:24:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:19:03 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:14:02 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:09:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 04:04:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:59:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:54:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:49:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:44:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:39:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:34:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:29:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:24:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:19:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:14:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:09:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 03:04:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:59:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:54:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:49:13 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:44:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:39:11 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:34:10 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:29:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:24:13 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:19:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:14:12 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:09:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 02:04:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:59:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:54:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:49:13 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:44:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:39:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:34:15 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:29:14 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:24:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:19:18 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:14:17 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:09:16 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:04:20 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 01:00:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:55:03 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:50:03 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:45:02 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:40:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:35:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:30:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:25:04 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:20:08 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:15:07 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:10:06 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:05:05 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |
2025-06-01 00:00:09 | !3738.30N/12029.62Er Shandong Longkou APRS 144.640Mhz | BG4IOK-10>AP51G5,TCPIP*,qAC,T2YANTAI:!3738.30N/12029.62ErShandong Longkou APRS 144.640Mhz |