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
20260208200003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t87r...p...P...h21b09189
20260208203003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t87r...p...P...h20b09189
20260208210003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t86r...p...P...h21b09189
20260208213003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t85r...p...P...h23b09190
20260208220003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t83r...p...P...h25b09191
20260208223004CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t82r...p...P...h26b09193
20260208230003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t81r...p...P...h29b09193
20260208233003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t79r...p...P...h31b09197
20260209000003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t76r...p...P...h34b09200
20260209003003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t74r...p...P...h39b09204
20260209010003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t72r...p...P...h42b09202
20260209013003CA3EVY-3>APDW16,TCPIP*,qAS,CA3EVY:!3335.50S/07030.80W_.../...g...t71r...p...P...h44b09209