APRS Packet Errors for DK7BW-11 (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
20260209121305DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223
20260209124328DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223
20260209131353DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223
20260209134417DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=067/A=000223
20260209141440DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=069/A=000223
20260209144502DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=069/A=000223
20260209151527DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223
20260209154550DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223
20260209161614DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=067/A=000223
20260209164638DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=067/A=000223
20260209171701DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223
20260209174724DK7BW-11>APRSGW,TCPIP*,qAR,DK7BW-11:!5216.29N/00802.96E#/B=068/A=000223