APRS Packet Errors for DB0TEK-10 (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
20260208164324DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208171339DB0TEK-10>APRSMC,TCPIP*,qAR,DO8PZ-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208174354DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208181409DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208184424DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208191439DB0TEK-10>APRSMC,TCPIP*,qAR,DL4ML-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208194454DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208201509DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208204524DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208211539DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208211655DB0TEK-10>APRSMC,TCPIP*,qAR,DB0MW-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208214554DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260208221609DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523