APRS Packet Errors for CA3EVY-3 (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
20260209133003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t68r...p...P...h53b09209
20260209140003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t70r...p...P...h51b09208
20260209143002CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t72r...p...P...h49b09207
20260209150003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t74r...p...P...h47b09206
20260209153003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t75r...p...P...h46b09205
20260209160003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t78r...p...P...h45b09204
20260209163003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t79r...p...P...h42b09202
20260209170003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t80r...p...P...h41b09199
20260209173003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t82r...p...P...h39b09196
20260209180003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t83r...p...P...h38b09193
20260209183004CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t85r...p...P...h36b09190
20260209190003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t86r...p...P...h33b09189