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
20260112233034FW2332>APRS,TCPXX*,qAX,CWOP-5:/122328z4737.94N/12235.79W_111/-000g000t052P034h94b10269L034FW2332 130027Z 110-00KT 10SM OVC003 11/10 A3032 RMK AO2 SLP269 T01110103=
20260112233632FW2332>APRS,TCPXX*,qAX,CWOP-4:/122334z4737.94N/12235.79W_108/-000g000t052P034h95b10267L029FW2332 130033Z 110-00KT 10SM OVC003 11/10 A3032 RMK AO2 SLP267 T01110103=
20260113023116FW2332>APRS,TCPXX*,qAX,CWOP-7:/130231z4737.94N/12235.79W_316/-000g000t052P000h98b10265L001FW2332 130330Z 320-00KT 10SM BKN003 11/10 A3031 RMK AO2 SLP265 T01110108=
20260113040546FW2332>APRS,TCPXX*,qAX,CWOP-7:/130405z4737.94N/12235.79W_179/-000g000t053P000h97b10263L001FW2332 130505Z 180-00KT 10SM SCT003 11/11 A3031 RMK AO2 SLP263 T01170112=