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
20260209121205DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209124221DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260209131239DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209134254DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260209141307DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209144322DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209151337DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209154352DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/A=000180
20260209161407DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209164422DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209171437DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180
20260209174455DL6YJB-1>APRSGW,TCPIP*,qAR,DL6YJB-1:!5138.52N/00720.58E-/B=100/A=000180