APRS Packet Errors for KE0YOM-7 (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
20260209134644KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[192/000/A=004059HT_BTech_DMR-6x2
20260209141646KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[192/000/A=004083HT_BTech_DMR-6x2
20260209145508KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[125/000/A=004134HT_BTech_DMR-6x2
20260209152558KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[125/000/A=004107HT_BTech_DMR-6x2
20260209162657KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[333/000/A=004137HT_BTech_DMR-6x2
20260209171204KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[333/000/A=004116HT_BTech_DMR-6x2
20260209174206KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[333/000/A=004137HT_BTech_DMR-6x2
20260209181208KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[333/000/A=004128HT_BTech_DMR-6x2
20260209184214KE0YOM-7>APBT62,WA6IFI-12*,qAR,K0XK-5:!3816.18N/10428.88W[333/000/A=004101HT_BTech_DMR-6x2
20260209191215KE0YOM-7>APBT62,WIDE2-2,qAR,N0HAX:!3816.18N/10428.88W[333/000/A=004122HT_BTech_DMR-6x2