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
20260209094101DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209101110DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=053/A=000095
20260209104124DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209111134DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209114147DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=052/A=000095
20260209121156DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209124207DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209131217DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209134230DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209141240DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=055/A=000095
20260209144955DN9JTR-1>APRSGW,TCPIP*,qAR,DN9JTR-1:!5258.66N/00823.87E-#DN9JTR-1/B=053/A=000095