APRS Packet Errors for LX1YCV-9 (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
20251027103530LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@103527h4937.50N/00600.860b025/219Mate LX1YCV
20251027111530LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@11526.h4937.36N/006.6119Eb065/000Mate LX1YCV
20251027115223LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@115220h4937.41N/0000.593Eb244/000Mate LX1YCV
20251027115832LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@115829h4937.41N/00600.660b025/070Mate LX1YCV
20251027121054LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@121050h4937.42N/006.7024Eb253/001Mate LX1YCV
20251027123529LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@123526h4937.41N/00600690Eb247/000Mate LX1YCV
20251027130004LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@125958h4937.410/E0b025/074Mate LX1YCV
20251027130611LX1YCV-9>APBM1D,DMR*,qAS,DL3OCK-12:@130608h4937.38/00600.72Eb058/001Mate LX1YCV