APRS Packet Errors for GW4219 (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
20250115000122GW4219>APRS,TCPXX*,qAX,CWOP-5:@150001z3510.82N/10156.23W_045/NaNg000t040r000p000P000h55b10258 VISR3924 400
20250115001122GW4219>APRS,TCPXX*,qAX,CWOP-4:@150011z3510.82N/10156.23W_045/NaNg000t040r000p000P000h55b10258 VISR3924 400
20250115013143GW4219>APRS,TCPXX*,qAX,CWOP-6:@150131z3510.82N/10156.23W_135/NaNg000t033r000p000P000h66b10267 VISR3924 400
20250115014122GW4219>APRS,TCPXX*,qAX,CWOP-7:@150141z3510.82N/10156.23W_135/NaNg000t033r000p000P000h66b10267 VISR3924 400
20250115025122GW4219>APRS,TCPXX*,qAX,CWOP-3:@150251z3510.82N/10156.23W_158/NaNg000t028r000p000P000h72b10275 VISR3924 400
20250115030123GW4219>APRS,TCPXX*,qAX,CWOP-3:@150301z3510.82N/10156.23W_158/NaNg000t028r000p000P000h72b10275 VISR3924 400