APRS Packet Errors for DN9JTR-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
20260208163438DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208170449DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208173502DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=053/A=000095
20260208180512DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208183527DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=053/A=000095
20260208190536DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208193548DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208200558DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208203610DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208210620DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208213634DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260208220645DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095