APRS Packet Errors for K2ZA-1 (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
20251026221811K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251026224506K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251026231542K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251026233731K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251027000555K2ZA-1>APX219,CLAYTN,KB2EAR-1,WIDE2*,qAR,KC2MDN-2:;W2MMD-R *270005z3943.6N/07501.91Wr147.180MHz X1S= +060 R20m Net Su8pm
20251027000733K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251027003843K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251027010646K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm
20251027012801K2ZA-1>APX219,TCPIP*,qAC,T2PERTH:)147.180+_3943.66N/07507.91Wr+060 T131 R20m Net Su8pm