APRS Packet Errors for DL2JA-2 (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
20260208130906DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=071/A=001673
20260208133921DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=072/A=001673
20260208140936DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=071/A=001673
20260208143953DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=073/A=001673
20260208151008DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=070/A=001673
20260208154020DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=071/A=001673
20260208161035DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=071/A=001673
20260208164050DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=071/A=001673
20260208171107DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=070/A=001673
20260208174122DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=074/A=001673
20260208181134DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=072/A=001673
20260208184149DL2JA-2>APRSGW,TCPIP*,qAR,DL2JA-2:!4825.38N/01147.20E#/B=070/A=001673