APRS Packet Errors for FW7700 (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
20260615074039FW7700>APRS,TCPXX*,qAX,CWOP-4:@150740z4005.37N/07620.21W_30/003g004t067r000p001P001h90b10047wund
20260615075100FW7700>APRS,TCPXX*,qAX,CWOP-7:@150750z4005.37N/07620.21W_60/002g003t066r000p001P001h87b10051wund
20260615081142FW7700>APRS,TCPXX*,qAX,CWOP-7:@150811z4005.37N/07620.21W_87/004g006t065r000p001P001h85b10051wund
20260615090327FW7700>APRS,TCPXX*,qAX,CWOP-3:@150903z4005.37N/07620.21W_77/001g002t063r000p001P001h89b10054wund
20260615100533FW7700>APRS,TCPXX*,qAX,CWOP-5:@151005z4005.37N/07620.21W_47/002g002t062r000p001P001h90b10064wund
20260615103636FW7700>APRS,TCPXX*,qAX,CWOP-3:@151036z4005.37N/07620.21W_82/001g001t063r000p001P001h88b10068wund
20260615115924FW7700>APRS,TCPXX*,qAX,CWOP-5:@151159z4005.37N/07620.21W_38/002g002t066r000p001P001h81b10081wund
20260615120945FW7700>APRS,TCPXX*,qAX,CWOP-4:@151209z4005.37N/07620.21W_37/004g006t066r000p001P001h74b10078wund
20260615122006FW7700>APRS,TCPXX*,qAX,CWOP-7:@151220z4005.37N/07620.21W_63/002g003t066r000p001P001h71b10085wund