A total of 564 recevied packets have been found for station/object EA3HVF-DP between 06/02/2025 10:31:39 AM+00:00 and 06/05/2025 10:31:39 AM+00:00.
Request took 0.038 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 564 packets.
[>] 06/05/2025 10:18:09 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 06/05/2025 10:18:09 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 06/05/2025 10:16:23 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/05/2025 10:16:23 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 06/05/2025 9:47:57 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 06/05/2025 9:47:57 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 06/05/2025 9:45:41 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/05/2025 9:45:41 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 06/05/2025 9:17:33 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 06/05/2025 9:17:33 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 06/05/2025 9:14:59 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/05/2025 9:14:59 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 06/05/2025 8:47:18 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 06/05/2025 8:47:18 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 06/05/2025 8:44:12 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/05/2025 8:44:12 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 06/05/2025 8:17:07 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 06/05/2025 8:17:07 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 06/05/2025 8:13:33 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/05/2025 8:13:33 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 06/05/2025 7:46:56 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 06/05/2025 7:46:56 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 06/05/2025 7:42:42 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 434.1000 MHz
[>] 06/05/2025 7:42:42 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 06/05/2025 7:16:35 AM+00:00:
EA3HVF>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 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.