APRS Packet Errors for SL5ZYT-1 (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
20190423103010SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423110011SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423110051SL5ZYT-1>WIDE2-2,qAS,SA5JAR-1:;CONTEN-10*181715z5836.15N/01719.00E
20190423113009SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423120010SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423123011SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423123052SL5ZYT-1>WIDE2-2,qAS,SA5JAR-1:;CONTEN-10*181715z5836.15N/01719.00E
20190423130010SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423133011SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423140010SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423143011SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423150009SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423153010SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E
20190423160011SL5ZYT-1>APU25N,TCPIP*,qAC,T2BIO:;CONTEN-10*181715z5836.15N/01719.00E