A total of 144 recevied packets have been found for station/object BI3TTR-10 between 07/03/2025 1:37:05 PM+00:00 and 07/06/2025 1:37:05 PM+00:00.
Request took 0.018 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 144 packets.
[>] 07/06/2025 1:09:52 PM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 12:39:52 PM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 12:09:52 PM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 11:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 11:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 10:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 10:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 9:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 9:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 8:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 8:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 7:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 7:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 6:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 6:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 5:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 5:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 4:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 4:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 3:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 3:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 2:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 2:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 1:39:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
[>] 07/06/2025 1:09:52 AM+00:00:
BI3TTR-10>APDW16,TCPIP*,qAC,T2TOKYO:!3407.41NI10849.83E&PHG0100APRS iGate over 144.640M; Also report 438.650M APRS for SSC Prj;
* 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.