APRS Packet Errors for DG1KW-9 (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
20260209131709DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.92E#Meshcom client /B=100/A=000210
20260209134708DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.92E#Meshcom client /B=100/A=000246
20260209141711DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.93E#Meshcom client /B=100/A=000210
20260209144709DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.17N/00652.92E#Meshcom client /B=100/A=000233
20260209151709DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.92E#Meshcom client /B=100/A=000200
20260209154711DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.92E#Meshcom client /B=100/A=000148
20260209161714DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.92E#Meshcom client /B=100/A=000226
20260209164711DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.91E#Meshcom client /B=100/A=000190
20260209171720DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.93E#Meshcom client /B=100/A=000282
20260209174710DG1KW-9>APRSMC,TCPIP*,qAR,DG1KW-12:!5125.16N/00652.92E#Meshcom client /B=100/A=000217