APRS Packet Errors for DG3HS-25 (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
20260209131419DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000118
20260209134434DG3HS-25>APRSMC,TCPIP*,qAR,DO7FJK-15:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000125
20260209141503DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000112
20260209151520DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000118
20260209161550DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000121
20260209171620DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000148
20260209174635DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000121
20260209181650DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=099/A=000135
20260209184707DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000121