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
20260208151842N3TJJ-10>APOTC1,WIDE1-1,qAR,N3TJJ-11:!3959.30N/07618.75Wr 14.0V-04C
20260208154350N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 14.0V-04C
20260208160858N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.9V-04C
20260208163403N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.9V-02C
20260208165909N3TJJ-10>APOTC1,WIDE1-1,qAR,W3AD-1:!3959.30N/07618.75Wr 13.9V-02C
20260208172409N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.6V-02C
20260208174911N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.6V-02C
20260208181412N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.9V 00C
20260208183913N3TJJ-10>APOTC1,WIDE1-1,qAR,N3TJJ-11:!3959.30N/07618.75Wr 14.0V-02C
20260208190417N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 14.0V-02C
20260208192918N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.5V 00C
20260208195419N3TJJ-10>APOTC1,WIDE1-1,qAR,N3TJJ-11:!3959.30N/07618.75Wr 13.9V 00C
20260208201922N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 14.0V 00C
20260208204423N3TJJ-10>APOTC1,WIDE1-1,qAR,N3FYI-2:!3959.30N/07618.75Wr 13.2V 00C