APRS Packet Errors for DL6YJB-1 (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
20260208150104DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260208153119DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260208160134DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=008/A=000180
20260208160204DL6YJB-1>APRSMC,TCPIP*,qAR,DB0SEP-12:!5138.52N/00720.58E-/B=008/A=000180
20260208163149DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260208170204DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260208173219DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260208180234DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=011/A=000180
20260208183250DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260208190308DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260208193323DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260208200338DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260208203353DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180