APRS Packet Errors for W3WOR (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
20260208131758W3WOR>APRS,WIDE1-1,WIDE2-1,qAR,N3XKU:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208134815W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208141816W3WOR>APRS,WIDE1-1,WIDE2-1,qAR,NQ3U-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208144817W3WOR>APRS,WIDE1-1,WIDE2-1,qAR,N3XKU:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208151819W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208154820W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208161822W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208164823W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208171824W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208174826W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208181827W3WOR>APRS,WIDE1-1,qAO,KC3ELT-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700
20260208184829W3WOR>APRS,WIDE1-1,WIDE2-1,qAR,NQ3U-10:!4038.64N/07521.76W-PHG3250/A=000455TMD700