A total of 57 recevied packets have been found for station/object EA1AYL-DP between 05/30/2025 9:27:15 PM+00:00 and 06/02/2025 9:27:15 PM+00:00.
Request took 0.106 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 57 packets.
[>] 06/02/2025 9:16:46 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 8:45:56 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 8:15:08 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 7:44:21 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 7:13:36 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 6:42:54 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 6:12:05 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 5:41:17 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 5:10:39 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 4:39:57 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 4:09:04 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 3:38:10 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 3:07:09 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 2:36:18 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 2:05:42 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 1:35:08 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 1:04:23 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 12:33:33 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 12:02:43 PM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 11:31:54 AM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 11:01:05 AM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 10:30:29 AM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 9:59:53 AM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 9:29:07 AM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 MHz
[>] 06/02/2025 8:58:32 AM+00:00:
EA1AYL>APZDMR,QTH*,TCPIP*,qAU,T2KOBLENZ:)EA1AYL-DP!4329.44N/00609.05WrRNG0034 IPSC2-EA4Master MMDVM 433.2500 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...