APRS Packet Errors for W6MAF (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
20190425045000W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,KF6NXQ-15:_04242149c252s01f009t061r000p060P006h57b10165tU2k
20190425045001W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,AF6UA-10:_04242149c252s01f009t061r000p060P006h57b10165tU2kj
20190425045007W6MAF>APTW01,KF6ILA-10,KD6DCN-5,KA6DAC-1,WIDE2*,qAR,N6SUN-10:_04242149c252s01f009t061r000p060P006h57b10165tU2kX
20190425045057W6MAF>APTW01,KF6ILA-10,N6EX-4,qAR,W6HRO:_04242149c252s01f009t061r000p060P006h57b10165tU2k
20190425062429W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,KF6NXQ-15:_04242324c26s011g009t060r000p000P000h63b10157tU2k
20190425062429W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,AF6UA-10:_04242324c26s011g009t060r000p000P000h63b10157tU2k
20190425062430W6MAF>APTW01,KF6ILA-10,KF6ILA*,qAR,AF6UA-10:_04242324c26s011g009t060r000p000P000h63b10157tU2k