APRS Packet Errors for HA7CQ-51 (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
20260209104034HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209111037HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209114040HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209121044HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209124047HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209131050HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209134054HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209141057HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209144100HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209151103HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209154106HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT
20260209161110HA7CQ-51>APLRG1,TCPIP*,qAC,T2ERFURT:=4730.80NL01848.69E-LoRa_APRS_PATY_ZSAMBEKI_UT