APRS Packet Errors for DL1SX-12 (last 6 hours)

This table contains packets in which findU has detected an error. This is an automated system, no manual checking of these packets has been done. Most common cause of this is mistakes in entering the latitude/longitude into hard-coded digis, or positions of 0/0. If packets of yours appear here, and you have looked at it carefully and cannot find the error, look again. I've been watching these error messages in my log, and believe my parser is reasonably correct. Go get the APRS spec to be sure. If you have done that, and are CERTAIN the packet is a legal APRS packet, then it is possible that there is an error in my my parser. Only email me if you are absolutely, positively certain...ask yourself, would I bet $100!

time (UTC)Packet
20260208135332DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t042r...p...P...h73b10119LoRa APRS iGate 433.775 MHz
20260208143332DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t041r...p...P...h73b10119LoRa APRS iGate 433.775 MHz
20260208151332DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t041r...p...P...h72b10120LoRa APRS iGate 433.775 MHz
20260208155333DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t040r...p...P...h72b10122LoRa APRS iGate 433.775 MHz
20260208163333DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t040r...p...P...h73b10123LoRa APRS iGate 433.775 MHz
20260208171334DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t039r...p...P...h73b10126LoRa APRS iGate 433.775 MHz
20260208175334DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t039r...p...P...h73b10127LoRa APRS iGate 433.775 MHz
20260208183334DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t039r...p...P...h73b10127LoRa APRS iGate 433.775 MHz
20260208191334DL1SX-12>APLRG1,TCPIP*,qAC,T2SYDNEY:!L4!0xQ4_e_ xG.../...g...t039r...p...P...h73b10127LoRa APRS iGate 433.775 MHz