APRS Packet Errors for DG7LAY-15 (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
20260208170712DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=100/A=000033
20260208173724DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=085/A=000033
20260208180739DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=100/A=000033
20260208183806DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=100/A=000033
20260208190809DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=100/A=000033
20260208200839DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=075/A=000033
20260208203856DG7LAY-15>APRSMC,TCPIP*,qAR,DB0HEI-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=092/A=000033
20260208210909DG7LAY-15>APRSMC,TCPIP*,qAR,DB0HEI-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=100/A=000033
20260208213924DG7LAY-15>APRSMC,TCPIP*,qAR,DB0HEI-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=100/A=000033
20260208220945DG7LAY-15>APRSMC,TCPIP*,qAR,DB0XN-12:!5430.20N/00935.28E#MeshCom M13#DG7LAY-15/B=070/A=000033