A total of 309 recevied packets have been found for station/object EA3HVF-DP between 08/26/2025 4:27:26 AM+00:00 and 08/29/2025 4:27:26 AM+00:00.
Request took 0.005 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 309 packets.
[>] 08/29/2025 4:05:30 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 4:05:30 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 4:03:34 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 3:35:11 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 3:35:11 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 3:32:44 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 3:04:52 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 3:04:52 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 3:02:20 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 2:34:23 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 2:34:23 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 2:31:38 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 2:04:05 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 2:04:05 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 2:00:44 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 1:33:26 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 1:33:26 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 1:29:51 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 1:03:07 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 1:03:07 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 12:59:03 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 12:32:49 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.57ErRNG0034 IPSC2-EA3Master MMDVM 432.2000 MHz
[>] 08/29/2025 12:32:49 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.98N/00202.58ErRNG0034 IPSC2-EA3Master MMDVM 439.9000 MHz
[>] 08/29/2025 12:28:41 AM+00:00:
EA3HVF>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HVF-DP!4122.99N/00202.60ErRNG0034 IPSC2-EA4Master MMDVM 435.1000 MHz
[>] 08/29/2025 12:02:40 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.