A total of 123 recevied packets have been found for station/object EA1RKL-R between 07/07/2025 8:56:05 AM+00:00 and 07/10/2025 8:56:05 AM+00:00.
Request took 0.008 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 123 packets.
[>] 07/10/2025 8:30:07 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131521z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 8:00:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131451z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 7:30:19 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131421z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 7:00:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131351z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 6:30:07 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131321z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 6:00:08 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131251z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 5:00:08 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131151z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 4:30:10 AM+00:00:
ED1YAP-3>APMI01,ED1ZAP-3,WIDE2*,qAR,CQ0PBR:;EA1RKL-R *131121z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 4:00:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131051z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 3:30:08 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *131021z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 3:00:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130951z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 2:30:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130921z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 2:00:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130851z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 1:30:09 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130821z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 1:00:11 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130751z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 12:30:10 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130721z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/10/2025 12:00:10 AM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130651z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 11:30:10 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130621z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 11:00:11 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130551z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 10:30:10 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130521z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 10:00:13 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130451z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 9:30:11 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130421z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 8:30:11 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130321z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 8:00:12 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130251z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
[>] 07/09/2025 7:30:13 PM+00:00:
ED1YAP-3>APMI01,WIDE2-1,qAR,ED1ZAR-3:;EA1RKL-R *130221z4304.44N/00717.48Wr145.237MHz T077 E.Link Conf. CZR
* 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.