A total of 29 recevied packets have been found for station/object EA4AES-DP between 06/03/2025 2:28:31 PM+00:00 and 06/06/2025 2:28:31 PM+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 29 packets.
[>] 06/06/2025 12:25:14 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/06/2025 11:54:24 AM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/06/2025 11:23:37 AM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/06/2025 10:52:40 AM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 8:00:45 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 7:29:53 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 6:59:04 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 6:28:16 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 5:57:31 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 5:26:54 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/05/2025 4:56:09 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 7:25:38 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 6:54:49 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 6:24:07 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 5:53:16 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 12:15:20 PM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 11:44:41 AM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 11:13:55 AM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 10:43:13 AM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/04/2025 10:12:38 AM+00:00:
EA4AES>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/03/2025 7:51:04 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/03/2025 7:20:19 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/03/2025 6:49:17 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/03/2025 6:18:26 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 MHz
[>] 06/03/2025 5:47:36 PM+00:00:
EA4AES>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AES-DP!3923.27N/00311.86WrRNG0034 IPSC2-EA4Master MMDVM 434.9500 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.