A total of 289 recevied packets have been found for station/object SP2JGY-10 between 07/03/2025 5:36:28 PM+00:00 and 07/06/2025 5:36:28 PM+00:00.
Request took 0.023 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 289 packets.
[>] 07/06/2025 5:32:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@173226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 5:17:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@171726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 5:02:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@170226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 4:47:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@164726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 4:32:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@163226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 4:17:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@161726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 4:02:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@160226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 3:47:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@154726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 3:32:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@153226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 3:17:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@151726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 3:02:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@150226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 2:47:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@144726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 2:32:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@143226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 2:17:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@141726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 2:02:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@140226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 1:47:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@134726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 1:32:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@133226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 1:17:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@131726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 1:02:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@130226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 12:47:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@124726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 12:32:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@123226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 12:17:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@121726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 12:02:24 PM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@120226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 11:47:24 AM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@114726h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
[>] 07/06/2025 11:32:24 AM+00:00:
SP2JGY-10>APWW11,TCPIP*,qAC,T2CZECH:@113226h5410.60N/01800.26E#PHG5230iGate+Digi | Tiny Win XP (SBC) , TNC2
* 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.