APRS Packet Errors for W0CTS-15 (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
20260208183200W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@081832z3809.23N/10243.17W/APRSD Beacon
20260208190201W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@081902z3809.23N/10243.17W/APRSD Beacon
20260208193201W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@081932z3809.23N/10243.17W/APRSD Beacon
20260208200202W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082002z3809.23N/10243.17W/APRSD Beacon
20260208203202W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082032z3809.23N/10243.17W/APRSD Beacon
20260208210203W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082102z3809.23N/10243.17W/APRSD Beacon
20260208213204W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082132z3809.23N/10243.17W/APRSD Beacon
20260208220204W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082202z3809.23N/10243.17W/APRSD Beacon
20260208223205W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082232z3809.23N/10243.17W/APRSD Beacon
20260208230205W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082302z3809.23N/10243.17W/APRSD Beacon
20260208233206W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@082332z3809.23N/10243.17W/APRSD Beacon
20260209000207W0CTS-15>APZ100,TCPIP*,qAC,T2TEXAS:@090002z3809.23N/10243.17W/APRSD Beacon