APRS Packet Errors for IZ4AKM (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
20260209132111IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209133113IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209134115IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209135117IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209140119IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209141121IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209142123IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209143127IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209144129IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209145131IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit
20260209150133IZ4AKM>APBM1D,IR2UDL,DMR*,qAR,IR2UDL:@015857h4502.18N/00939.62E(121/000Command and TLC Unit