APRS Packet Errors for N2EDX-10 (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
20260208181746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@081817z2905.16N/08059.30WI
20260208184746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@081847z2905.16N/08059.30WI
20260208191746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@081917z2905.16N/08059.30WI
20260208194746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@081947z2905.16N/08059.30WI
20260208201746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082017z2905.16N/08059.30WI
20260208204746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082047z2905.16N/08059.30WI
20260208211746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082117z2905.16N/08059.30WI
20260208214746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082147z2905.16N/08059.30WI
20260208221746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082217z2905.16N/08059.30WI
20260208224746N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082247z2905.16N/08059.30WI
20260208230127N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082301z2905.16N/08059.30WI
20260208233115N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@082331z2905.16N/08059.30WI
20260209000114N2EDX-10>APMI06,TCPIP*,qAC,T2PERTH:@090001z2905.16N/08059.30WI