LoRa APRS Track Direct

☰

reset

SQ5JP-4 Raw Packets

This is the latest recevied packets stored in our database for station/object SQ5JP-4. If no packets are shown the sender has not sent any packets the latest 24 hours.

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.

<< 1 2 >>

1760382509: SQ5JP-4>APLRG1,TCPIP*,qAC,T2BC:!L4,svSy7"_ G.../...g...t043h99b10037LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760378908: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CAEAST:!L4,svSy7"_ G.../...g...t042h99b10036LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760375308: SQ5JP-4>APLRG1,TCPIP*,qAC,T2TAS:!L4,svSy7"_ G.../...g...t043h00b10037LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760374408: SQ5JP-4>APLRG1,TCPIP*,qAC,T2TAS:!L4,svSy7"_ G.../...g...t043h00b10038LoRa iGate 434.855 @ 1k2 Batt=4.16V

1760373509: SQ5JP-4>APLRG1,TCPIP*,qAC,T2TAS:>https://github.com/richonguzman/LoRa_APRS_iGate 2025.03.20

1760373508: SQ5JP-4>APLRG1,TCPIP*,qAC,T2TAS:!L4,svSy7"_ GSQ5JP-4>APLRG1,WIDE1-1,qLoRa iGate 434.855 @ 1k2 Batt=4.16V

1760371713: SQ5JP-4>APLRG1,TCPIP*,qAC,T2PERTH:!L4,svSy7"_ G.../...g...t043h00b10037LoRa iGate 434.855 @ 1k2 Batt=4.16V

1760368112: SQ5JP-4>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4,svSy7"_ G.../...g...t046h99b10035LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760364512: SQ5JP-4>APLRG1,TCPIP*,qAC,T2PERTH:!L4,svSy7"_ G.../...g...t048h92b10036LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760360911: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CHILE:!L4,svSy7"_ G.../...g...t047h92b10041LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760360011: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CHILE:!L4,svSy7"_ G.../...g...t049h83b10040LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760357310: SQ5JP-4>APLRG1,TCPIP*,qAC,T2UKRAINE:!L4,svSy7"_ G.../...g...t051h76b10040LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760353709: SQ5JP-4>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4,svSy7"_ G.../...g...t050h78b10045LoRa iGate 434.855 @ 1k2 Batt=4.16V

1760352809: SQ5JP-4>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4,svSy7"_ G.../...g...t053h76b10046LoRa iGate 434.855 @ 1k2 Batt=4.16V

1760351909: SQ5JP-4>APLRG1,TCPIP*,qAC,T2SYDNEY:>https://github.com/richonguzman/LoRa_APRS_iGate 2025.03.20

1760351908: SQ5JP-4>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4,svSy7"_ GSQ5JP-4>APLRG1,WIDE1-1,qLoRa iGate 434.855 @ 1k2 Batt=4.16V

1760350109: SQ5JP-4>APLRG1,TCPIP*,qAC,T2PERTH:!L4,svSy7"_ G.../...g...t053h80b10048LoRa iGate 434.855 @ 1k2 Batt=4.16V

1760346509: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CHILE:!L4,svSy7"_ G.../...g...t050h89b10051LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760342908: SQ5JP-4>APLRG1,TCPIP*,qAC,T2SPAIN:!L4,svSy7"_ G.../...g...t046h00b10053LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760339308: SQ5JP-4>APLRG1,TCPIP*,qAC,T2TAS:!L4,svSy7"_ G.../...g...t042h00b10053LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760335707: SQ5JP-4>APLRG1,TCPIP*,qAC,T2PANAMA:!L4,svSy7"_ G.../...g...t038h00b10053LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760332106: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CAEAST:!L4,svSy7"_ G.../...g...t035h00b10052LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760331206: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CAEAST:!L4,svSy7"_ G.../...g...t035h00b10050LoRa iGate 434.855 @ 1k2 Batt=4.17V

1760330307: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CAEAST:>https://github.com/richonguzman/LoRa_APRS_iGate 2025.03.20

1760330306: SQ5JP-4>APLRG1,TCPIP*,qAC,T2CAEAST:!L4,svSy7"_ GSQ5JP-4>APLRG1,WIDE1-1,qLoRa iGate 434.855 @ 1k2 Batt=4.15V

Select date and time to show map data for (enter time for your locale time zone). The regular time length select box can still be used to select how old data that should be shown (relative to selected date and time).

*Note that the heatmap will still based on data from the latest hour (not the selected date and time).

Date and time:

Maintained by I8FUC, based on APRS Track Direct