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
20250624141520MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8o5TIsy_H_Q.../...g...t100h19b10191
20250624142521MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8o4TIsh_HOQ.../...g...t100h19b10175
20250624163849MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-11:!/8qATItK_I#Q.../...g...t100h18b10226
20250624164849MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8pSTItX_HwQ.../...g...t100h19b10219
20250624165850MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8q+TItM_HLQ.../...g...t099h18b10177
20250624170850MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8q"TItQ_HkQ.../...g...t099h18b10208
20250624172835MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8pNTIt>_H]Q.../...g...t098h18b10196
20250624174835MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-11:!/8ocTIsy_HNQ.../...g...t098h18b10182
20250624184216MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-10:!/8o;TIsJ_HEQ.../...g...t096h19b10179
20250624192418MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-11:!/8lDTIrX_FcQ.../...g...t095h20b10060
20250624195357MTCGPS-1>APLRT1,WIDE1-1,qAR,LZ0VRC-11:!/8kYTIr*_FWQ.../...g...t094h19b10054