APRS Packet Errors for W6MAF (last 24 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
20190117223421W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,KF6NXQ-15:!3822.)0N/11724.50W_PHG6150/A=003980/Oak Hmls WXTrak
20190117223422W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,AF6UA-10:!3822.)0N/11724.50W_PHG6150/A=003980/Oak Hmls WXTrak+M
20190117223423W6MAF>APTW01,KF6ILA-10,XE2GF-10*,WIDE2-1,qAR,N6EAJ:!3822.)0N/11724.50W_PHG6150/A=003980/Oak Hmls WXTrakz
20190117223424W6MAF>APTW01,KF6ILA-10,XE2GF-10,KA6DAC-1,WIDE2*,qAR,N6EAJ:!3822.)0N/11724.50W_PHG6150/A=003980/Oak Hmls WXTrakR
20190118025746W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,KF6NXQ-15:_01171857c252s08g005t049r000p027P047h88b10169T2k
20190118025747W6MAF>APTW01,KF6ILA-10*,WIDE2-2,qAR,AF6UA-10:_01171857c252s08g005t049r000p027P047h88b10169T2k5
20190118025748W6MAF>APTW01,KF6ILA-10,KF6ILA*,qAR,N6SUN-10:_01171857c252s08g005t049r000p027P047h88b10169T2k̋
20190118105958W6MAF>APTW01,KELLER,WIDE1,XE2GF-10,KF6ILA-10,WIDE2*,qAR,KF6NXQ-15:!3422.10N/11724.50W_0HG6)50/A=003980/Oak Hills WXRrak
20190118163305W6MAF>APTW01,AD6TS,WIDE1,KF6ILA-10*,qAR,KF6NXQ-15:_01180832c267s0$8g008t045r000p027P000h00b10200tU2k
20190118163306W6MAF>APTW01,AD6TS,WIDE1,KF6ILA-10*,qAR,AF6UA-10:_01180832c267s0$8g008t045r000p027P000h00b10200tU2kF