APRS Packet Errors for DH0TG-2 (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
20260208163616DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=005/A=001266
20260208170631DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=100/A=001266
20260208173647DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=002/A=001266
20260208180702DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=024/A=001266
20260208183717DH0TG-2>APRSMC,TCPIP*,qAR,DF4ND-99:!4927.76N/01053.28E##DH0TG-2/B=079/A=001266
20260208190732DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=008/A=001266
20260208193746DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=100/A=001266
20260208200801DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=009/A=001266
20260208203816DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=095/A=001266
20260208210831DH0TG-2>APRSMC,TCPIP*,qAR,DF4ND-99:!4927.76N/01053.28E##DH0TG-2/B=023/A=001266
20260208213846DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=043/A=001266
20260208220904DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/A=001266