A total of 300 recevied packets have been found for station/object EA1IQY-10 between 06/02/2025 11:45:27 AM+00:00 and 06/05/2025 11:45:27 AM+00:00.
Request took 0.02 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 300 packets.
[>] 06/05/2025 11:37:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t073h49b10087LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 11:22:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t075h47b10087LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 11:07:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t072h50b10086LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 10:52:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t071h51b10086LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 10:37:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t073h48b10085LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 10:22:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t071h50b10084LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 10:07:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t070h52b10084LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 9:52:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t070h50b10085LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 9:37:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t073h47b10085LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 9:22:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t072h48b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 9:07:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t074h46b10084LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 8:52:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t074h46b10084LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 8:37:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t072h48b10085LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 8:22:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t069h51b10082LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 8:07:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t073h47b10084LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 7:52:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t073h46b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 7:37:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t074h45b10084LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 7:22:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t073h46b10085LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 7:07:23 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:>https://github.com/richonguzman/LoRa_APRS_iGate 2025.03.20
[>] 06/05/2025 7:07:22 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t070h49b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 7:02:32 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t072h47b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 6:47:32 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t071h47b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 6:32:32 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t072h48b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 6:17:32 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t072h48b10083LoRa Mos iGate + Fill-In digi
[>] 06/05/2025 6:02:32 AM+00:00:
EA1IQY-10>APLRG1,TCPIP*,qAC,T2SPAIN:!4212.34NL00836.08W_.../...t071h48b10082LoRa Mos iGate + Fill-In digi
* 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...