APRS Packet Errors for DL3LP-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
20260208125807DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000823
20260208132828DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.28E#F12#Lothar/B=100/A=000758
20260208135850DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000801
20260208142911DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000797
20260208145932DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000791
20260208152954DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000817
20260208160015DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.30E#F12#Lothar/B=100/A=000787
20260208163036DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.30E#F12#Lothar/B=100/A=000784
20260208170058DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000768
20260208173120DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000846
20260208180142DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.28E#F12#Lothar/B=100/A=000784
20260208183203DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.04N/00925.29E#F12#Lothar/B=100/A=000801