APRS Packet Errors for DF2RS-12 (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
20260209091902DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209094917DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209101932DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209104947DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209112004DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209115020DF2RS-12>APRSMC,TCPIP*,qAR,DL2MT-11:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209122031DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209125047DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209132100DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209135116DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209142131DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023
20260209145146DF2RS-12>APRSGW,TCPIP*,qAR,DF2RS-12:!5325.51N/00713.77E#DF2RS GW JO33OK/A=000023