APRS Packet Errors for DB2OM-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
20260208182718	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208185733	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208192748	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208195805	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208202818	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208205833	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208212849	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208215904	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208222919	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410
20260208225934	DB2OM-1>APRSMC,TCPIP*,qAR,DB2OM-12:!5200.66N/01008.33E[/B=100/A=000410