APRS Packet Errors for N3IJW (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
20260209130535N3IJW>APWW11,TCPIP*,qAC,T2RDU:@200535h3220.07N/11103.15W-Sean in NW Tucson
20260209133536N3IJW>APWW11,TCPIP*,qAC,T2RDU:@203535h3220.07N/11103.15W-Sean in NW Tucson
20260209140536N3IJW>APWW11,TCPIP*,qAC,T2RDU:@210536h3220.07N/11103.15W-Sean in NW Tucson
20260209143536N3IJW>APWW11,TCPIP*,qAC,T2RDU:@213536h3220.07N/11103.15W-Sean in NW Tucson
20260209150536N3IJW>APWW11,TCPIP*,qAC,T2RDU:@220536h3220.07N/11103.15W-Sean in NW Tucson
20260209153537N3IJW>APWW11,TCPIP*,qAC,T2RDU:@223536h3220.07N/11103.15W-Sean in NW Tucson
20260209160537N3IJW>APWW11,TCPIP*,qAC,T2RDU:@230536h3220.07N/11103.15W-Sean in NW Tucson
20260209163537N3IJW>APWW11,TCPIP*,qAC,T2RDU:@233537h3220.07N/11103.15W-Sean in NW Tucson
20260209170537N3IJW>APWW11,TCPIP*,qAC,T2RDU:@000537h3220.07N/11103.15W-Sean in NW Tucson
20260209173538N3IJW>APWW11,TCPIP*,qAC,T2RDU:@003537h3220.07N/11103.15W-Sean in NW Tucson
20260209180538N3IJW>APWW11,TCPIP*,qAC,T2RDU:@010538h3220.07N/11103.15W-Sean in NW Tucson
20260209183538N3IJW>APWW11,TCPIP*,qAC,T2RDU:@013538h3220.07N/11103.15W-Sean in NW Tucson