今天收到的 BD4TDG-5 45 APRS数据包 下载轨迹 aprs.fi hamclub 本站
时间 | msg | raw packet |
---|---|---|
2025-09-18 22:57:36 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 22:27:07 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 21:56:43 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 21:04:21 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 20:33:41 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 20:02:41 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 19:31:11 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 19:00:40 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 18:30:08 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 17:59:32 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 17:28:46 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 16:57:54 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 16:27:10 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 15:56:34 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 15:26:04 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 14:55:39 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 14:25:04 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 13:54:20 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 13:23:51 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 12:53:13 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 12:22:39 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 11:51:45 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 11:21:07 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 10:50:27 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 10:19:52 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 09:49:12 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 09:18:18 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 08:47:33 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 08:16:35 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 07:46:01 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 07:14:49 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 06:44:16 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 06:13:37 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 05:42:55 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 05:12:28 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 04:41:56 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 04:11:20 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 03:40:48 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 03:10:15 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 02:39:41 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 02:09:14 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 01:38:31 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 01:07:59 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 00:37:27 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |
2025-09-18 00:06:54 | !3453.06N/11911.31Er 144.640mhz lianyungang 0.3w 60m | BD4TDG-5>APLM3U,TCPIP*,qAC,T2TOKYO:!3453.06N/11911.31Er144.640mhz lianyungang 0.3w 60m |