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
20260209092140DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209095155DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209095232DB0TEK-10>APRSMC,TCPIP*,qAR,DB0AIS-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209102210DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209105225DB0TEK-10>APRSMC,TCPIP*,qAR,DO8PZ-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209112240DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209115255DB0TEK-10>APRSMC,TCPIP*,qAR,DL4ML-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209122310DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209125325DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209132340DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209135355DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209142410DB0TEK-10>APRSMC,TCPIP*,qAR,DL4ML-12:!4835.30N/00928.19E#MeshCom/A=002523
20260209145425DB0TEK-10>APRSMC,TCPIP*,qAR,DN7TMU-12:!4835.30N/00928.19E#MeshCom/A=002523