APRS Packet Errors for DB2GS (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
20260209120307DB0SWS>APU25N,qAR,F4FXL-3:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209123307DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209130307DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209133307DB0SWS>APU25N,qAR,F4FXL-3:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209140308DB0SWS>APU25N,qAR,F4FXL-3:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209143307DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209150308DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209153309DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209160307DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209163307DB0SWS>APU25N,qAR,F4FXL-3:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209170307DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach
20260209173308DB0SWS>APU25N,qAR,F5JFA-1:;DB2GS *131925z4834.60N/00810.43E-Werner in Seebach