APRS Packet Errors for DA6YPJ-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
20260208145954DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=010/A=000440
20260208150006DA6YPJ-1>APRSMC,TCPIP*,qAR,DB0CRE-12:!5138.65N/00715.10E#/B=010/A=000440
20260208153005DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=019/A=000440
20260208160020DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=022/A=000440
20260208163035DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=011/A=000440
20260208170050DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=030/A=000440
20260208173105DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=016/A=000440
20260208180121DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=017/A=000440
20260208183136DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=031/A=000440
20260208190147DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=022/A=000440
20260208193202DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=021/A=000440
20260208200217DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.10E#/B=019/A=000440
20260208203232DA6YPJ-1>APRSGW,TCPIP*,qAR,DA6YPJ-1:!5138.65N/00715.11E#/B=030/A=000440