APRS Packet Errors for CQ0PTD (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
20260208163312CQ0PTD>APDW18,WIDE2-2,qAO,CT2GSW-10:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208170311CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208173311CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208180311CQ0PTD>APDW18,WIDE2-2,qAR,ED1ZAJ-3:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208183312CQ0PTD>APDW18,WIDE2-2,qAR,ED1ZAJ-3:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208190311CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208193311CQ0PTD>APDW18,WIDE2-2,qAO,CT2GSW-10:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208200312CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208203311CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208210311CQ0PTD>APDW18,WIDE2-2,qAO,CT2GSW-10:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208213311CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD
20260208220311CQ0PTD>APDW18,WIDE2-2,qAR,CT1ALX:!4113.39N/00801.54W#PHG3670W2 ARETD