APRS Packet Errors for DH1BUZ-12 (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
20250211072644DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_0008+&..t026h94b10250 TTGO-LoRa_WX-Gatowj
20250211074941DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_000/00...t026h91b10250 TTGO-LoRa_WX-GatowNNN
20250211092235DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/013 49E_000o44ecNNNT10h76b10250 WTGi79NNNR(h
20250211102558DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.498p*..t032h69b10240 TTGO-LoRa_WX-GatowNNN
20250211120737DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_00008.~0Ib}%sML&ä@f;Rj: ijXgK
20250211123456DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!52%3308.<=A_&=mk.97kNNNb192X~I.KSa_WX-Gdt+