APRS Packet Errors for VE2CXP-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
20260928003500VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000/73
20260928003510VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928003549VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928003639VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928003719VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928003809VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928003858VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928020520VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928020600VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928020640VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928020719VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928020759VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000
20260928020839VE2CXP-1>APT311,WIDE3-3,qAR,VE2LPO:!0000.000/00000.000k000/000