APRS Packet Errors for N1UKJ-15 (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
20250314182059N1UKJ-15>APAT81-2,WIDE1-1,WIDE2-1,qAR,WERNER:!4017.:0N/10650.:0W[/A=007211APRSCN
20250314183601N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314185803N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314192005N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314193106N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314194206N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314195308N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314200408N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314210305N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314211406N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314212508N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314213609N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878
20250314214711N1UKJ-15>APBM1D,N1UKJ,DMR*,qAR,N1UKJ:@015857h4017.:0N/10650.:0WY000/000AT878