APRS Packet Errors for VK4JRO-3 (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
20260208151246VK4JRO-3>APTT4,VK4RSR-3*,WIDE2-2,qAS,VK4VP-4:/011512z2525.72S/15207.04E#/A=002198
20260208154245VK4JRO-3>APTT4,VK4RSR-3*,WIDE2-2,qAS,VK4VP-4:/011542z2525.72S/15207.04E#/A=002225
20260208164259VK4JRO-3>APTT4,VK4RSR-3*,WIDE2-2,qAR,VK4RMC-3:/011642z2525.71S/15207.04E#/A=002215
20260208171259VK4JRO-3>APTT4,VK4RBO-3,WIDE1*,WIDE2-2,qAR,VK4RTQ-3:/011712z2525.71S/15207.04E#/A=002182
20260208174314VK4JRO-3>APTT4,VK4RBO-3,WIDE1*,WIDE2-2,qAR,VK4RTQ-3:/011743z2525.71S/15207.04E#/A=002198
20260208181315VK4JRO-3>APTT4,VK4REG-3,WIDE1*,WIDE2-2,qAR,VK4RTQ-3:/011813z2525.71S/15207.04E#/A=002189
20260208184330VK4JRO-3>APTT4,VK4RPR-3,WIDE1*,WIDE2-2,qAR,VK4RAI-3:/011843z2525.71S/15207.04E#/A=002166
20260208191340VK4JRO-3>APTT4,VK4RSR-3*,WIDE2-2,qAS,VK4VP-4:/011913z2525.72S/15207.04E#/A=002202
20260208194339VK4JRO-3>APTT4,VK4RSR-3*,WIDE2-2,qAS,VK4VP-4:/011943z2525.71S/15207.04E#/A=002169
20260208204410VK4JRO-3>APTT4,WIDE1-1,WIDE2-2,qAO,VK4BW:/012044z2525.71S/15207.04E#/A=002198