APRS Packet Errors for OE3CJB-4 (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
20260208182012OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208185027OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208192042OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208195057OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208202115OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208205130OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208212145OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208215200OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208222219OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208225234OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208232249OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869
20260208235306OE3CJB-4>APRSGW,TCPIP*,qAR,OE3CJB-4:!4813.62N/01539.85E[Meshcom#Chris/A=000869