APRS Packet Errors for IU2UCK (last 24 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
20250827052329IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@052326h0000.00N/00000.00E[000/000Alessandro
20250827052633IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@052630h0000.00N/00000.00E[000/000Alessandro
20250827052937IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@052934h0000.00N/00000.00E[000/000Alessandro
20250827053240IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@053237h0000.00N/00000.00E[000/000Alessandro
20250827053544IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@053541h0000.00N/00000.00E[000/000Alessandro
20250827141628IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@141625h0000.00N/00000.00E[000/000Alessandro
20250827141932IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@141929h0000.00N/00000.00E[000/000Alessandro
20250827144106IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@144100h0000.00N/00000.00E[000/000Alessandro
20250827145743IU2UCK>APBM1D,IR2ZYE,DMR*,qAR,IR2ZYE:@145740h0000.00N/00000.00E[000/000Alessandro