今天收到的 BI1NFI-1 105 APRS数据包 下载轨迹 aprs.fi hamclub hellocq 本站 本站轨迹
| 时间 | msg | raw packet |
|---|---|---|
| 2024-04-30 08:34:38 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 08:29:39 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 08:24:40 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 08:19:41 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 08:14:42 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 08:09:42 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 08:04:43 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:59:44 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:54:45 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:49:46 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:44:47 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:39:47 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:34:48 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:29:49 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:24:50 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:19:51 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2NANJING:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:16:08 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:11:09 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:06:10 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 07:03:41 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:58:42 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:53:43 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:48:44 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:43:45 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:38:46 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:33:46 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:28:47 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2YANTAI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:23:48 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:18:49 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:13:50 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:08:51 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 06:03:52 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:58:53 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:53:53 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:48:54 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2YANTAI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:43:55 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2YANTAI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:38:56 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:33:57 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:28:58 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:23:59 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:18:59 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:14:00 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:09:01 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 05:04:02 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:59:03 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:54:03 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:49:04 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:44:05 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:39:06 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:34:07 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:29:08 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:24:09 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:19:09 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:14:10 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:09:11 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 04:04:12 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:59:13 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:54:14 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:49:15 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:44:15 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:39:16 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2YANTAI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:34:17 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:29:18 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2YANTAI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:24:19 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2YANTAI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:19:20 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:14:20 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:09:21 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 03:04:22 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:59:20 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:54:21 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:49:22 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:44:23 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:39:23 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2FUKUOKA:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:36:13 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:29:25 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:24:25 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:19:26 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:14:27 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:09:28 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 02:04:29 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:59:30 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:54:30 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:49:31 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:44:32 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:39:33 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:34:34 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:29:35 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:24:35 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:19:36 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:14:37 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:09:38 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 01:04:39 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:59:40 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:54:41 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:49:41 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:44:42 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:39:43 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:34:44 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:29:44 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:24:45 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:19:46 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:14:47 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:09:48 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:04:49 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |
| 2024-04-30 00:00:05 | !4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz | BI1NFI-1>APLM3U,TCPIP*,qAC,T2TAIPEI:!4008.35N/11706.29ErBEIJING PINGGU APRS IGATE 144.640MHz |