APRS Packet Errors for MTCGPS-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
20250918154410MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8'7TII#_GfQ.../...g...t084h18b10269
20250918155410MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8'3TIHA_HGQ.../...g...t084h18b10324
20250918160410MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8(#TIHm_GTQ.../...g...t083h18b10257
20250918162456MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8&qTIHm_H,Q.../...g...t083h19b10301
20250918164910MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8)oTIIJ_E$Q.../...g...t083h19b10109
20250918175514MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8\%?TIGg_GWQ.../...g...t084h18b10271
20250918180514MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-11:!/8&cTII>_I)Q.../...g...t084h19b10400
20250918181514MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8(ETII!_GgQ.../...g...t084h19b10286
20250918182515MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8+TTIGd_HvQ.../...g...t083h19b10388