APRS Packet Errors for G7JYM (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
20260209132120G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@132119h5129.28N/00010.63W-APRS-IS for Win32
20260209135121G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@135120h5129.28N/00010.63W-APRS-IS for Win32
20260209142121G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@142121h5129.28N/00010.63W-APRS-IS for Win32
20260209145122G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@145122h5129.28N/00010.63W-APRS-IS for Win32
20260209152123G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@152123h5129.28N/00010.63W-APRS-IS for Win32
20260209155124G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@155123h5129.28N/00010.63W-APRS-IS for Win32
20260209162125G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@162124h5129.28N/00010.63W-APRS-IS for Win32
20260209165125G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@165125h5129.28N/00010.63W-APRS-IS for Win32
20260209172126G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@172125h5129.28N/00010.63W-APRS-IS for Win32
20260209175126G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@175126h5129.28N/00010.63W-APRS-IS for Win32
20260209182127G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@182126h5129.28N/00010.63W-APRS-IS for Win32
20260209185128G7JYM>APWW11,TCPIP*,qAC,T2ROMANIA:@185127h5129.28N/00010.63W-APRS-IS for Win32