APRS Packet Errors for OE5ERN-13 (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
20260209144647OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209151700OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209154715OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209161725OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209164738OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209171751OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209174804OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209181816OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209184829OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209191842OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209194854OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843
20260209201907OE5ERN-13>APRSMC,TCPIP*,qAR,OE5ERN-12:!4819.62NN01418.01E#MeshCom#Node/B=098/A=000843