APRS Packet Errors for PMC (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
20260208151036PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208153036PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208153634PMC>APN383,STJOHN*,WIDE2-1,qAR,BASHOR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208163037PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208163634PMC>APN383,WIDE2-2,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208165037PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208171037PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208172037PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208173037PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208173635PMC>APN383,STJOHN*,WIDE2-1,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208185037PMC>APN383,qAR,STLUBR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com
20260208193635PMC>APN383,TNGNXI*,WIDE2-1,qAR,BASHOR:!3907.62n/09447.19whPHG7330 W2, MOn-N KCHEART.KC0HRT@gmail.com