APRS Packet Errors for FW0562 (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
20260209120832FW0562>APN000,TCPXX*,qAX,CWOP-3:@091208z5049.17N/00432.88E_147/002g007t044r000p001P001b10039h86eMB63
20260209123831FW0562>APN000,TCPXX*,qAX,CWOP-4:@091238z5049.17N/00432.88E_166/003g007t044r000p001P001b10036h85eMB63
20260209133832FW0562>APN000,TCPXX*,qAX,CWOP-5:@091338z5049.17N/00432.88E_174/003g010t046r000p001P001b10030h83eMB63
20260209140835FW0562>APN000,TCPXX*,qAX,CWOP-5:@091408z5049.17N/00432.88E_171/004g010t046r000p001P001b10028h82eMB63
20260209143833FW0562>APN000,TCPXX*,qAX,CWOP-5:@091438z5049.17N/00432.88E_157/002g010t046r000p001P001b10027h82eMB63
20260209150832FW0562>APN000,TCPXX*,qAX,CWOP-3:@091508z5049.17N/00432.88E_131/001g008t046r000p001P001b10024h82eMB63
20260209153832FW0562>APN000,TCPXX*,qAX,CWOP-4:@091538z5049.17N/00432.88E_137/001g007t047r000p001P001b10021h82eMB63
20260209163835FW0562>APN000,TCPXX*,qAX,CWOP-6:@091638z5049.17N/00432.88E_146/000g006t044r000p001P001b10016h85eMB63
20260209170847FW0562>APN000,TCPXX*,qAX,CWOP-7:@091708z5049.17N/00432.88E_149/000g005t043r000p001P001b10014h86eMB63
20260209173844FW0562>APN000,TCPXX*,qAX,CWOP-6:@091738z5049.17N/00432.88E_197/000g003t042r000p001P001b10013h88eMB63