APRS Packet Errors for N7ZEV-4 (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
20130522012437N7ZEV-4>APN391,VEGAS*,WIDE2*,qAR,K7MPR-10:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522022436N7ZEV-4>APN391,WR7NV-1,WIDE2*,qAR,KA7STK-10:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522025435N7ZEV-4>APN391,RODMAN,WIDE2*,qAo,N6VIG:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522032436N7ZEV-4>APN391,VEGAS,WIDE2*,qAR,K6RBK:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522035440N7ZEV-4>APN391,RODMAN,WIDE2*,qAo,N6VIG:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522042436N7ZEV-4>APN391,WR7NV-1,WIDE2*,qAR,KA7STK-10:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522045436N7ZEV-4>APN391,WR7NV-1*,WIDE2-1,qAR,KA7STK-10:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522052437N7ZEV-4>APN391,WR7NV-1,WIDE2*,qAR,KA7STK-10:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522062437N7ZEV-4>APN391,WR7NV-1,WIDE2*,qAR,KA7STK-10:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada
20130522065437N7ZEV-4>APN391,HAYDEN*,WIDE2,qAR,KD6GHX:!3645.55N11407.18W#PHG3360W3,NVc-4 New DIGI in Mesquite Nevada