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
20260208150323DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000108
20260208153336DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000128
20260208160348DG3HS-25>APRSMC,TCPIP*,qAR,DB7HT-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000125
20260208163403DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000118
20260208170418DG3HS-25>APRSMC,TCPIP*,qAR,DO1LKG-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000121
20260208173439DG3HS-25>APRSMC,TCPIP*,qAR,DL8HAV-12:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000121
20260208180448DG3HS-25>APRSMC,TCPIP*,qAR,DB7HT-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000085
20260208183503DG3HS-25>APRSMC,TCPIP*,qAR,DB7HT-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000135
20260208193537DG3HS-25>APRSMC,TCPIP*,qAR,DB7HT-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000125
20260208200553DG3HS-25>APRSMC,TCPIP*,qAR,DB7HT-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000118
20260208203611DG3HS-25>APRSMC,TCPIP*,qAR,DB7HT-25:!5345.82N/01015.94E-Node JO53DS#Elmenhorst/B=100/A=000131