APRS Packet Errors for DH5DAN-99 (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
20260208145516DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=079/A=000190
20260208152531DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=100/A=000190
20260208155549DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=100/A=000190
20260208162604DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=100/A=000190
20260208165615DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=100/A=000190
20260208172630DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=100/A=000190
20260208175645DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=098/A=000190
20260208182703DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=097/A=000190
20260208185718DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=096/A=000190
20260208192731DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=095/A=000190
20260208195746DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=093/A=000190
20260208202801DH5DAN-99>APRSGW,TCPIP*,qAR,DH5DAN-99:!5135.48N/00720.98E##MeshDash-SQL/B=094/A=000190