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
20180720101218SL5ZYT-1>APU25N,TCPIP*,qAC,T2SWEDEN2:;CONTEN-10*181715z5836.15N/01719.00E
20180720104218SL5ZYT-1>WIDE2-2,qAR,SM0RGQ-11:;CONTEN-10*181715z5836.15N/01719.00E
20180720111218SL5ZYT-1>APU25N,TCPIP*,qAC,T2SWEDEN2:;CONTEN-10*181715z5836.15N/01719.00E
20180720114216SL5ZYT-1>APU25N,TCPIP*,qAC,T2SWEDEN2:;CONTEN-10*181715z5836.15N/01719.00E
20180720121218SL5ZYT-1>WIDE2-2,qAR,SM0RGQ-11:;CONTEN-10*181715z5836.15N/01719.00E
20180720124217SL5ZYT-1>WIDE2-2,qAR,SL5ZYT-3:;CONTEN-10*181715z5836.15N/01719.00E
20180720131218SL5ZYT-1>WIDE2-2,qAR,SM0RGQ-11:;CONTEN-10*181715z5836.15N/01719.00E
20180720134218SL5ZYT-1>WIDE2-2,qAR,SL5ZYT-3:;CONTEN-10*181715z5836.15N/01719.00E
20180720144218SL5ZYT-1>WIDE2-2,qAR,SM0RGQ-11:;CONTEN-10*181715z5836.15N/01719.00E
20180720144307SL5ZYT-1>APU25N,TCPIP*,qAC,T2SWEDEN2:;CONTEN-10*181715z5836.15N/01719.00E
20180720151217SL5ZYT-1>WIDE2-2,qAR,SL5ZYT-3:;CONTEN-10*181715z5836.15N/01719.00E
20180720154217SL5ZYT-1>APU25N,TCPIP*,qAC,T2SWEDEN2:;CONTEN-10*181715z5836.15N/01719.00E