APRS Packet Errors for DL2DBR-91 (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
20260209114019DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=050/A=000942
20260209121034DL2DBR-91>APRSMC,TCPIP*,qAR,DN9MIC-12:!5050.61N/00758.64E#/B=100/A=000942
20260209124049DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=056/A=000942
20260209131104DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=100/A=000942
20260209134119DL2DBR-91>APRSMC,TCPIP*,qAR,DN9MIC-12:!5050.61N/00758.64E#/B=100/A=000942
20260209141135DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=100/A=000942
20260209144155DL2DBR-91>APRSMC,TCPIP*,qAR,DO5RBB-12:!5050.61N/00758.64E#/B=100/A=000942
20260209151204DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=100/A=000942
20260209154222DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=057/A=000942
20260209161234DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=050/A=000942
20260209164250DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=100/A=000942
20260209171305DL2DBR-91>APRSMC,TCPIP*,qAR,DG3DJ-12:!5050.61N/00758.64E#/B=056/A=000942