APRS Packet Errors for N6ZOZ-7 (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
20250615080456N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@015857h3702.:0N/12202.27Wk000/000N6ZOZ
20250615080755N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@080753h3702.:0N/12202.27Wk000/000N6ZOZ
20250615081111N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@081109h3702.:0N/12202.27Wk000/000N6ZOZ
20250615081721N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@081719h3702.:0N/12202.27Wk000/000N6ZOZ
20250615081740N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@081739h3702.:0N/12202.27Wk000/000N6ZOZ
20250615081851N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@081850h3702.:0N/12202.27Wk000/000N6ZOZ
20250615081954N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@081953h3702.:0N/12202.27Wk000/000N6ZOZ
20250615082035N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@082033h3702.:0N/12202.27Wk000/000N6ZOZ
20250615082133N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@082132h3702.:0N/12202.27Wk000/000N6ZOZ
20250615082340N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@082339h3702.:0N/12202.27Wk000/000N6ZOZ
20250615084233N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@084232h3702.:0N/12202.27Wk000/000N6ZOZ
20250615234116N6ZOZ-7>APBM1D,N6ZOZ,DMR*,qAR,N6ZOZ:@015857h3702.:0N/12202.27Wk000/000N6ZOZ