APRS Packet Errors for VK5RHO-1 (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
20260208165222VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208172247VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208175314VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208182338VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208185406VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208192430VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208205547VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208212611VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208215637VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE
20260208222703VK5RHO-1>APNU19,ADEL2-2,qAR,VK5ZX-5:!3449.29SS13845.32E#PHG5720/Adelaide NEast Ui-Digi PF95JE