A total of 52 recevied packets have been found for station/object SP2JGY-15 between 07/23/2025 9:19:16 AM+00:00 and 07/26/2025 9:19:16 AM+00:00.
Request took 0.006 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 52 packets.
[>] 07/25/2025 11:54:46 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 11:22:43 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 10:52:42 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 10:22:40 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 9:54:39 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 9:22:38 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 8:52:36 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 8:22:31 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 7:54:29 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.32V !w!*!
[>] 07/25/2025 7:22:26 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 6:52:23 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 6:22:21 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 5:54:19 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.32V !w!*!
[>] 07/25/2025 5:22:18 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 4:52:16 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 4:22:14 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 3:54:12 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 3:22:10 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 2:52:09 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 2:22:07 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 1:54:05 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.34V !w!*!
[>] 07/25/2025 1:22:03 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
[>] 07/25/2025 12:52:01 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.32V !w!*!
[>] 07/25/2025 12:21:59 PM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.32V !w!*!
[>] 07/25/2025 11:53:57 AM+00:00:
SP2JGY-15>APLOX1,TCPIP*,qAC,T2UK:!5410.60NL01800.26E#LoRa Digi/iGate @ 434.855MHz 1200bps 73! P=4.33V !w!*!
* 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...