A total of 139 recevied packets have been found for station/object EA3HLC-DP between 07/05/2025 4:48:30 PM+00:00 and 07/08/2025 4:48:30 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 139 packets.
[>] 07/08/2025 4:40:29 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 4:09:50 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 3:39:19 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 3:08:49 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 2:37:57 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 2:07:16 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 1:36:37 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 1:05:56 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 12:35:16 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 12:04:36 PM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 11:33:57 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 11:03:18 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 10:32:36 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 10:01:56 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 9:31:16 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 9:00:36 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 8:29:55 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 7:59:13 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 7:28:24 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 6:57:44 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 6:27:04 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 5:56:23 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 5:25:33 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 4:54:53 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 MHz
[>] 07/08/2025 4:24:14 AM+00:00:
EA3HLC>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA3HLC-DP!4134.98N/00137.98ErRNG0034 IPSC2-EA3Master MMDVM 434.3000 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.
Snapshot Active 
Filter Active 
Map Wizard Active 
Please wait while the map is redrawn...