APRS Packet Errors for DO1BZH-10 (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
20260208165440DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=078/A=000007
20260208172452DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=078/A=000007
20260208175507DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=077/A=000007
20260208182522DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=077/A=000007
20260208185538DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=078/A=000007
20260208192553DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=078/A=000007
20260208195604DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=078/A=000007
20260208202619DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=078/A=000007
20260208205634DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=077/A=000007
20260208212651DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=076/A=000007
20260208215706DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=077/A=000007
20260208222721DO1BZH-10>APRSGW,TCPIP*,qAR,DO1BZH-10:!5429.08N/00851.09Eu/B=077/A=000007