A total of 285 recevied packets have been found for station/object EA3ANS-DP between 06/05/2025 3:11:24 AM+00:00 and 06/08/2025 3:11:24 AM+00:00.
Request took 0.016 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 285 packets.
[>] 06/08/2025 2:49:48 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/08/2025 2:48:36 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/08/2025 2:19:18 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/08/2025 2:18:26 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/08/2025 1:48:36 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/08/2025 1:48:15 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/08/2025 1:18:05 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/08/2025 1:17:56 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/08/2025 12:47:55 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/08/2025 12:47:16 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/08/2025 12:17:45 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/08/2025 12:16:35 AM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 11:47:34 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/07/2025 11:45:55 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 11:17:24 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/07/2025 11:15:34 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 10:47:14 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/07/2025 10:45:05 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 10:17:04 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/07/2025 10:14:26 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 9:46:53 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/07/2025 9:43:34 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 9:16:41 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 MHz
[>] 06/07/2025 9:12:54 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-EA3Master MMDVM 438.8000 MHz
[>] 06/07/2025 8:46:30 PM+00:00:
EA3ANS>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA3ANS-DP!4132.58N/00153.57ErRNG0034 IPSC2-Catalunya MMDVM 438.8000 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.