A total of 126 recevied packets have been found for station/object EA5EEF-DP between 06/15/2025 9:37:57 PM+00:00 and 06/18/2025 9:37:57 PM+00:00.
Request took 0.015 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 126 packets.
[>] 06/18/2025 9:28:16 PM+00:00:
EA5EEF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 9:28:16 PM+00:00:
EA5EEF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 9:16:22 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 8:57:29 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 8:57:29 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 8:45:42 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 8:26:36 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 8:26:36 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 8:15:03 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 7:56:03 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 7:56:03 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 7:44:25 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 7:25:11 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 7:25:11 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 7:13:48 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 6:54:36 PM+00:00:
EA5EEF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 6:54:36 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 6:43:10 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 6:23:59 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 6:23:59 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 6:12:32 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 5:53:08 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/18/2025 5:53:07 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA4Master MMDVM 436.5500 MHz
[>] 06/18/2025 5:41:53 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3736.84N/00102.77WrRNG0034 IPSC2-EA-Hotspot MMDVM 438.0250 MHz
[>] 06/18/2025 5:22:33 PM+00:00:
EA5EEF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA5EEF-DP!3740.70N/00103.26ErRNG0034 IPSC2-EA4Master MMDVM 438.1750 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.