A total of 421 recevied packets have been found for station/object EA4AIV-DP between 06/02/2025 4:34:46 PM+00:00 and 06/05/2025 4:34:46 PM+00:00.
Request took 0.022 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 421 packets.
[>] 06/05/2025 4:24:59 PM+00:00:
EA4AIV>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 4:24:59 PM+00:00:
EA4AIV>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 4:24:59 PM+00:00:
EA4AIV>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 3:54:09 PM+00:00:
EA4AIV>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 3:54:09 PM+00:00:
EA4AIV>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 3:54:09 PM+00:00:
EA4AIV>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 3:23:23 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 3:23:23 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 3:23:23 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 2:52:34 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 2:52:34 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 2:52:34 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 2:21:48 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 2:21:48 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 2:21:48 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 1:51:05 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 1:51:05 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 1:51:05 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 1:20:23 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 1:20:23 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 1:20:23 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 12:49:49 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 MHz
[>] 06/05/2025 12:49:49 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.42N/00355.60WrRNG0034 IPSC2-EA4Master MMDVM 433.7750 MHz
[>] 06/05/2025 12:49:49 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.12N/00355.71WrRNG0034 IPSC2-EA4Master MMDVM 438.1750 MHz
[>] 06/05/2025 12:19:07 PM+00:00:
EA4AIV>APZDMR,QTH,TCPIP*,qAU,T2KOBLENZ:)EA4AIV-DP!3859.43N/00355.61WrRNG0034 IPSC2-EA4Master MMDVM 434.4500 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.