APRS Packet Errors for DK9WE-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
20260209121232DK9WE-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052
20260209133833DK9WE-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052
20260209141156DK9WE-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052
20260209150845DK9WE-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052
20260209160455DK9WE-12>APRSMC,TCPIP*,qAR,DB0SH-1:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052
20260209170515DK9WE-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052
20260209173233DK9WE-12>APRSMC,TCPIP*,qAR,DB0XN-12:!5439.09N/00922.59E#Meshcom M03#DK9WE/B=100/A=000052