APRS Packet Errors for FW6385 (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
20260208150038FW6385>APRS,TCPXX*,qAX,CWOP-3:@081500z3503.75S/13831.28E_180/006g...t063r...p...P000b10119h80L000eMB52
20260208160026FW6385>APRS,TCPXX*,qAX,CWOP-5:@081600z3503.75S/13831.28E_180/006g014t063r000p000P000b10118h77L000eMB52
20260208170024FW6385>APRS,TCPXX*,qAX,CWOP-6:@081700z3503.75S/13831.28E_180/006g013t062r000p000P000b10110h80L000eMB52
20260208180027FW6385>APRS,TCPXX*,qAX,CWOP-4:@081800z3503.75S/13831.28E_180/006g014t062r000p000P000b10110h79L000eMB52
20260208190026FW6385>APRS,TCPXX*,qAX,CWOP-7:@081900z3503.75S/13831.28E_180/005g012t062r000p000P000b10117h80L000eMB52
20260208200025FW6385>APRS,TCPXX*,qAX,CWOP-3:@082000z3503.75S/13831.28E_180/005g016t061r000p000P000b10121h83L000eMB52