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 3 4 >>

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

1754319838: SQ5JP-4>APLRG1,TCPIP*,qAC,T2PANAMA:!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