A total of 153 recevied packets have been found for station/object OE5YAP-23 between 07/22/2025 9:34:21 AM+00:00 and 07/25/2025 9:34:21 AM+00:00.
Request took 0.038 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 153 packets.
[>] 07/25/2025 9:28:08 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 9:18:08 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 9:08:03 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 8:58:03 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 8:48:03 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 8:37:58 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 8:27:58 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 8:17:53 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 8:07:48 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 7:57:48 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 7:47:48 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 7:37:43 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 7:27:43 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 7:17:38 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 7:07:38 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 6:57:33 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 6:47:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 6:37:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 6:27:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 6:17:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 6:07:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 5:57:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 5:47:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 5:37:28 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 07/25/2025 5:27:23 AM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
* 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.