APRS Packet Errors for 146.70-R2 (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
20260209091614VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209094616VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209101619VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209104621VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209111623VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209114626VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209121628VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209124631VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209131633VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209134636VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209141638VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart
20260209144641VK7RHT>APNX20,qAR,VK7HSE-1:;146.70-R2*111111z4253.69S/14714.19ErT141.3 R60k VK7RHT Hobart