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
20260209120811OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=084/A=000535
20260209123826OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=097/A=000535
20260209130839OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=097/A=000535
20260209133855OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=100/A=000535
20260209140910OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=086/A=000535
20260209143925OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=089/A=000535
20260209150940OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=094/A=000535
20260209153956OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=087/A=000535
20260209161008OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=081/A=000535
20260209164023OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=071/A=000535
20260209171038OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=075/A=000535
20260209174053OE3CZC-1>APRSGW,TCPIP*,qAR,OE3CZC-1:!4817.61N1627.07ELMeshcom Node/B=083/A=000535