APRS Packet Errors for DK3VX-11 (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
20260208151529DK3VX-11>APRSMC,TCPIP*,qAR,DO1LKG-25:!5340.90N/01008.80E-JO53bq#DK3VX, Uwe/B=100/A=000374
20260208154535DK3VX-11>APRSMC,TCPIP*,qAR,DL8HAV-12:!5340.90N/01008.80E-JO53bq#DK3VX, Uwe/B=100/A=000374
20260208161550DK3VX-11>APRSMC,TCPIP*,qAR,DL8HAV-12:!5340.90N/01008.80E-JO53bq#DK3VX, Uwe/B=100/A=000374
20260208164605DK3VX-11>APRSMC,TCPIP*,qAR,DL8HAV-12:!5340.90N/01008.80E-JO53bq#DK3VX, Uwe/B=100/A=000374
20260208171620DK3VX-11>APRSMC,TCPIP*,qAR,DL8HAV-12:!5340.90N/01008.80E-JO53bq#DK3VX, Uwe/B=100/A=000374
20260208174635DK3VX-11>APRSMC,TCPIP*,qAR,DB7HT-25:!5340.90N/01008.80E-JO53bq#DK3VX, Uwe/B=100/A=000374
20260208191726DK3VX-11>APRSMC,TCPIP*,qAR,DB7HT-25:!5340.90N/01008.80E-/B=100/A=000374
20260208194744DK3VX-11>APRSMC,TCPIP*,qAR,DL8HAV-12:!5340.90N/01008.80E-/B=100/A=000374
20260208201750DK3VX-11>APRSMC,TCPIP*,qAR,DO1LKG-25:!5340.90N/01008.80E-/B=100/A=000374
20260208204805DK3VX-11>APRSMC,TCPIP*,qAR,DL8HAV-12:!5340.90N/01008.80E-/B=100/A=000374