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
20260209091438DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=002/A=001266
20260209094454DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=005/A=001266
20260209101505DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/A=001266
20260209104520DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=031/A=001266
20260209111535DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=100/A=001266
20260209114553DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=036/A=001266
20260209121609DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=100/A=001266
20260209124620DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=025/A=001266
20260209131635DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=030/A=001266
20260209134651DH0TG-2>APRSMC,TCPIP*,qAR,DF4ND-99:!4927.76N/01053.28E##DH0TG-2/B=067/A=001266
20260209141706DH0TG-2>APRSMC,TCPIP*,qAR,DF4ND-99:!4927.76N/01053.28E##DH0TG-2/B=028/A=001266
20260209144721DH0TG-2>APRSGW,TCPIP*,qAR,DH0TG-2:!4927.76N/01053.28E##DH0TG-2/B=089/A=001266