APRS Packet Errors for ED7YAL-3 (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
20170430050544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430053544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430060544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430063544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430070544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430073544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430080544ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430083543ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430090543ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430093543ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430100543ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W
20170430103543ED7YAL-3>APRS,TCPIP*,qAC,T2SPAIN:!3744.02N/00331.07W