APRS Packet Errors for N3TEM-1 (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
20260208132200N3TEM-1>APTT4,KV3B-1,WIDE1*,WIDE2-1,qAO,W4TTU-10:/010000z3922.47N7710.50WUSolar Powered @14.4V, Mt. Airy, MD 93F
20260208135156N3TEM-1>APTT4,WIDE1-1,WIDE2-1,qAR,N3TCR-10:/010000z3922.47N7710.50WUSolar Powered @14.5V, Mt. Airy, MD 94F
20260208142153N3TEM-1>APTT4,WIDE1-1,WIDE2-1,qAR,N3TCR-10:/010000z3922.47N7710.50WUSolar Powered @14.4V, Mt. Airy, MD 95F
20260208145151N3TEM-1>APTT4,KV3B-1,WIDE1*,WIDE2-1,qAO,W4TTU-10:/010000z3922.47N7710.50WUSolar Powered @14.5V, Mt. Airy, MD 96F
20260208155145N3TEM-1>APTT4,N3KTX-2*,WIDE1,WIDE2-1,qAO,W4TTU-10:/010000z3922.47N7710.50WUSolar Powered @14.3V, Mt. Airy, MD 97F
20260208162143N3TEM-1>APTT4,WIDE1-1,WIDE2-1,qAR,N3TCR-10:/010000z3922.47N7710.50WUSolar Powered @14.3V, Mt. Airy, MD 97F
20260208185129N3TEM-1>APTT4,WIDE1-1,WIDE2-1,qAR,N3TCR-10:/010000z3922.47N7710.50WUSolar Powered @14.3V, Mt. Airy, MD 98F
20260208185231N3TEM-1>APTT4,N3KTX-2,N4YSA-6,WIDE1,W4VA-13,WIDE2*,qAo,KG4GIY:/010000z3922.47N7710.50WUSolar Powered @14.3V, Mt. Airy, MD 98F