APRS Packet Errors for DB2OM-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
20260209130141DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209133158DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=083/A=000410
20260209140213DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=083/A=000410
20260209143225DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209150240DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209153255DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=089/A=000410
20260209160312DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209163327DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209170342DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209173356DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209180408DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410
20260209183423DB2OM-12>APRSGW,TCPIP*,qAR,DB2OM-12:!5200.65N/01008.31E#/B=100/A=000410