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
20260209090815DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000797
20260209093836DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000810
20260209100857DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000797
20260209103919DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000814
20260209110940DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000814
20260209114001DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.04N/00925.29E#F12#Lothar/B=100/A=000879
20260209121023DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.06N/00925.30E#F12#Lothar/B=100/A=000951
20260209123714DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.05N/00925.30E#F12#Lothar/B=100/A=000932
20260209130735DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.28E#F12#Lothar/B=100/A=000797
20260209133757DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000801
20260209140818DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.29E#F12#Lothar/B=100/A=000797
20260209143839DL3LP-1>APRSGW,TCPIP*,qAR,DL3LP-1:!5116.03N/00925.30E#F12#Lothar/B=100/A=000807