A total of 56 recevied packets have been found for station/object EA4FFX-DP between 06/02/2025 4:01:07 PM+00:00 and 06/05/2025 4:01:07 PM+00:00.
Request took 0.007 seconds to find in our database.
Packet history is available for up to 3 days. Sign up for a free account to view 30 up to days history. Use [>] to decode with our packet packet decoder tool.
Displaying 1 - 25 of 56 packets.
[>] 06/05/2025 8:13:33 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/05/2025 7:42:42 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/05/2025 7:11:41 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 6:54:49 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 6:24:07 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 5:53:16 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 5:22:50 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 4:52:14 PM+00:00:
EA4FFX>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 4:21:24 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 3:50:41 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 3:19:55 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 2:48:56 PM+00:00:
EA4FFX>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 2:18:13 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 1:47:31 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 1:16:58 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 12:46:08 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 12:15:20 PM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 11:44:41 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 11:13:55 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 10:43:13 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 10:12:38 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 9:41:43 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 9:11:04 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 8:40:07 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
[>] 06/04/2025 8:09:29 AM+00:00:
EA4FFX>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4FFX-DP!4037.26N/00400.18WrRNG0034 IPSC2-EA4Master MMDVM 439.8125 MHz
* If you compare the raw packets with similar data from other websites it may differ (especially the path), the reason is that we are not collecting packets from the same APRS-IS servers. Each APRS-IS server performes duplicate filtering, and which packet that is considered to be a duplicate may differ depending on which APRS-IS server you receive your data from.