APRS Packet Errors for ZL2ASC (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
20260208144713ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208151714ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208154715ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208161716ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208164717ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208171722ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208174722ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208181723ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208184724ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208191725ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208194726ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH
20260208201727ZL2ASC>APX218,TCPIP*,qAC,FOURTH:=4116.50S/17317.68E-Home QTH