APRS Packet Errors for KE4HTS (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
20190618030231KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS
20190618031231KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS FM07wv
20190618031232KE4HTS>APN83,WIDE2-2,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 From Fluvanna County VA FM07wv de ke4hts*
20190618035732KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS FM07wv
20190618042231KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS
20190618045233KE4HTS>APN83,K4EME-3*,WIDE2,qAR,W4DHW-1:!3753.65117N/7805.25048W#PHG51300 From beautiful downtown FM07wv de KE4HTS
20190618050232KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS
20190618061232KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS FM07wv
20190618072233KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS
20190618074232KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS
20190618080237KE4HTS>APN83,KJ4RPW-3*,WIDE2,qAR,NO3B-10:!3753.65117N/7805.25048W#PHG51300 From beautiful downtown FM07wv de KE4HTS
20190618082232KE4HTS>APN83,qAR,W4KEL-12:!3753.65117N/7805.25048W#PHG51300 DE KE4HTS