APRS Packet Errors for OE3LDV-3 (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
20260208132137OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.13E>#TBEAM/B=100/A=000679
20260208135141OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.12E>#TBEAM/B=100/A=000709
20260208141806OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.12E>#TBEAM/B=100/A=000728
20260208141944OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.56N/01631.13E>#TBEAM/B=100/A=000745
20260208145001OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.13E>#TBEAM/B=100/A=000699
20260208152021OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.13E>#TBEAM/B=100/A=000725
20260208155040OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.12E>#TBEAM/B=100/A=000692
20260208162100OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.12E>#TBEAM/B=100/A=000771
20260208165120OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.56N/01631.12E>#TBEAM/B=100/A=000692
20260208172140OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.56N/01631.12E>#TBEAM/B=100/A=000719
20260208175201OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.55N/01631.12E>#TBEAM/B=100/A=000735
20260208182220OE3LDV-3>APRSMC,TCPIP*,qAR,OE3LDV-1:!4839.56N/01631.13E>#TBEAM/B=100/A=000604