APRS Packet Errors for AE4VP-2 (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
20260208144727AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@144727h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208151727AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@151727h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208154727AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@154727h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208161728AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@161728h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208164728AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@164728h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208171728AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@171728h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208174729AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@174729h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208181729AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@181729h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208184730AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@184730h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208191730AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@191730h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208194730AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@194730h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate
20260208201731AE4VP-2>APWW11,TCPIP*,qAC,T2SYDNEY:@201731h3605.87N208329.36W#PHG/280 W2/AE4VP Digi./IGate