APRS Packet Errors for VERDUN (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
20260208143405VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281
20260208151956VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281
20260208160546VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281
20260208165137VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281
20260208173727VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 13.9V/A=003281
20260208182318VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281
20260208190909VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281
20260208195500VERDUN>APTT4,BOER,WIDE1*,WIDE2-2,qAR,HARRY:/000000h5352.26NS12600.71W#000/000VE7RES 146.76- 100Hz 20C 14.0V/A=003281