APRS Packet Errors for VK3XCO-7 (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
20260531193231VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/193226h00.00N/000.00E> /A=000000 Sq1 To0C 425cV Sa3 GF0
20260531193644VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/193640h3739.61S/14453.4E> /A=000583 Sq6 To0C 349cV Sa3 GF1
20260531194005VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/194001h3738.9S/14453.1E> /A=000590 Sq10 To0C 333cV Sa5 GF1
20260531195238VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/195236h00.00N/000.00E> /A=000000 Sq0 To0C 576cV Sa0 GF0
20260531195345VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/195343h00.00N/000.00E> /A=000000 Sq1 To0C 371cV Sa0 GF0
20260531195452VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/195450h00.00N/000.00E> /A=000000 Sq2 To0C 367cV Sa0 GF0
20260531195559VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/195557h00.00N/000.00E> /A=000000 Sq3 To0C 360cV Sa0 GF0
20260531195707VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/195704h00.00N/000.00E> /A=000000 Sq4 To0C 350cV Sa0 GF0
20260531195814VK3XCO-7>APRS,WIDE2-1,qAO,VK3LEO-10:/195811h00.00N/000.00E> /A=000000 Sq5 To0C 342cV Sa3 GF0