APRS Packet Errors for FW2332 (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
20260112182839FW2332>APRS,TCPXX*,qAX,CWOP-4:/121828z4737.94N/12235.79W_149/-000g000t050P032h98b10286L048FW2332 121927Z 150-00KT 10SM OVC003 10/09 A3037 RMK AO2 SLP286 T01010098=
20260112183039FW2332>APRS,TCPXX*,qAX,CWOP-3:/121830z4737.94N/12235.79W_134/-000g000t050P032h98b10285L050FW2332 121929Z 130-00KT 10SM OVC003 10/09 A3037 RMK AO2 SLP285 T01010098=
20260112193513FW2332>APRS,TCPXX*,qAX,CWOP-7:/121932z4737.94N/12235.79W_172/-000g000t050P034h99b10277L065FW2332 122032Z 170-00KT 10SM OVC003 10/10 A3035 RMK AO2 SLP277 T01020101=
20260112195710FW2332>APRS,TCPXX*,qAX,CWOP-6:/121957z4737.94N/12235.79W_172/-000g000t051P034h99b10259L110FW2332 122056Z 170-00KT 10SM OVC003 10/10 A3030 RMK AO2 SLP259 T01050103=
20260112211950FW2332>APRS,TCPXX*,qAX,CWOP-3:/122117z4737.94N/12235.79W_111/-000g000t051P034h97b10268L050FW2332 122216Z 110-00KT 10SM OVC003 10/10 A3032 RMK AO2 SLP268 T01050102=
20260112220759FW2332>APRS,TCPXX*,qAX,CWOP-3:/122207z4737.94N/12235.79W_218/-000g000t051P034h96b10262L061FW2332 122307Z 220-00KT 10SM OVC003 10/10 A3030 RMK AO2 SLP262 T01080102=