A total of 125 recevied packets have been found for station/object OE5YAP-23 between 06/15/2025 8:58:22 PM+00:00 and 06/18/2025 8:58:22 PM+00:00.
Request took 0.577 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 125 packets.
[>] 06/18/2025 8:49:41 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 8:39:41 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 8:29:41 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 8:19:36 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 8:09:36 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 7:59:35 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 7:49:31 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 7:39:27 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 7:29:27 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 7:19:26 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 7:09:21 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 6:59:21 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 6:49:21 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 6:39:21 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 6:29:16 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 6:19:16 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 6:09:16 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 5:59:11 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 5:49:11 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 5:39:11 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 5:29:06 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 5:19:05 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 5:09:01 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 4:59:01 PM+00:00:
OE5YAP-23>APOTW1,TCPIP*,qAC,T2KA:!4815.63NL01303.22E&PHG01000/Raspi2 LoRa APRS IGate Shild RX 433.775 (no TX)
[>] 06/18/2025 4:49:01 PM+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.
Snapshot Active 
Filter Active 
Map Wizard Active 
Please wait while the map is redrawn...