APRS Packet Errors for N5VLZ-G (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
20260208132438N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208135438N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208142439N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208145439N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208152440N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208155440N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208162441N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208165442N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208172442N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208175443N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208182443N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32
20260208185443N5VLZ-G>APWW11,TCPIP*,qAC,T2PERTH:=3442.05N/09219.74W)APRS-IS for Win32