APRS Packet Errors for DB0SWS (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
20260209103315DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209110315DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209113315DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209120315DB0SWS>APU25N,qAR,F4FXL-3:=4834.60N100810.43E#Digi Seebach
20260209123315DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209130315DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209133316DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209140317DB0SWS>APU25N,qAR,F5JFA-1:=4834.60N100810.43E#Digi Seebach
20260209143315DB0SWS>APU25N,qAR,F4FXL-3:=4834.60N100810.43E#Digi Seebach
20260209150316DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach
20260209153316DB0SWS>APU25N,qAR,F5JFA-1:=4834.60N100810.43E#Digi Seebach
20260209160315DB0SWS>APU25N,qAO,DK0A-10:=4834.60N100810.43E#Digi Seebach