APRS Packet Errors for AE0TB-5 (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
20190115141819AE0TB-5>APOT21,N0XJA-4,WIDE1,KB0JBF-3,WIDE2*,qAR,AE0TB-6:;13YF֖ S1111z4230.58N/0922465Wr16.940MHz 6 -060 R30m Net Su9p Wloo/CF
20190115171025AE0TB-5>APOT21,KB0JBF-3,WIDE1*,WIDE2-1,qAR,N0XJA-4:;146.94-IA*111111z4230.58N/9224.65Wr146.940MHz T136 -060 R30m Net Sv3
20190115180057AE0TB-5>APOT21,KB0JBF-3,WIDE1*,WIDE2-1,qAR,AE0TB-6:;146.94-IA*111111z4230.58&&FfVvMFfFCF-6ff&m+v3
20190115204253AE0TB-5>APOT21,KB0JBF-3,WIDE1,W0MCW-3,WIDE2*,qAR,WA0SPF:;146.94-IA*111111V&33YӚf3&m Neu9poo/
20190115213336AE0TB-5>APOT21,KB0JBF-3,WIDE1,W0MCW-3,WIDE2*,qAR,WA0SPF:;14֖ &6{f3n33C6ff&m+6v3
20190116012521AE0TB-5>APOT21,KB0JBF-3,WIDE1*,WIDE2-1,qAR,AE0TB-6:;146.94-IA*11z4V{&&FfVvMYFoF- -060 R30et Suc{{{63
20190116022614AE0TB-5>APOT21,KB0JBF-3,WIDE1*,WIDE2-1,qAR,N0XJA-4:;146.94-IA*11111z4230.58N/09224.65Wr146.940MHz T1fm֣6v3