APRS Packet Errors for OE3CZC-1 (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
20260208132706OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=096/A=000535
20260208135721OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=084/A=000535
20260208142736OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=075/A=000535
20260208145751OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=076/A=000535
20260208152806OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=076/A=000535
20260208155819OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=080/A=000535
20260208162831OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=100/A=000535
20260208165846OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=081/A=000535
20260208172901OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=095/A=000535
20260208175916OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=085/A=000535
20260208182935OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=080/A=000535
20260208185950OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=081/A=000535