APRS Packet Errors for VK2LQ (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
20250123113947VK2LQ>APDW13,qAR,VK2BNC-1:!0000.00N/00000.00E-304/000/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123120252VK2LQ>APDW13,qAR,VK2BN-1:!0000.00N/00000.00E-149/000/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123121348VK2LQ>APDW13,qAR,VK2BN-1:!0000.00N/00000.00E-320/001/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123121900VK2LQ>APDW13,qAR,VK2BN-1:!0000.00N/00000.00E-278/001/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123122344VK2LQ>APDW13,qAR,VK2BNC-1:!0000.00N/00000.00E-338/000/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123123356VK2LQ>APDW13,qAR,VK2BNC-1:!0000.00N/00000.00E-133/000/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123125434VK2LQ>APDW13,qAR,VK2BN-1:!0000.00N/00000.00E-322/000/A=000000Hi All VK2LQ TG 505 DRIVE SAFE
20250123130150VK2LQ>APDW13,qAR,VK2BNC-1:!0000.00N/00000.00E-349/001/A=000000Hi All VK2LQ TG 505 DRIVE SAFE