APRS Packet Errors for N3TJJ-10 (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
20260209121149N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 12.7V-06C
20260209123658N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 12.8V-06C
20260209130200N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.6V-06C
20260209132705N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V-06C
20260209135207N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 14.0V-04C
20260209141709N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V-04C
20260209144210N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.6V-02C
20260209150713N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.6V-02C
20260209153213N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V 00C
20260209155716N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V 02C
20260209162225N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V 00C
20260209164729N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 14.0V 00C
20260209171230N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V 02C
20260209173732N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.6V 04C