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
20250330191945DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308&9C1$]1l}NNN*h>7_5b10080,TGO-LoRa_WX-GatowNNN
20250330195800DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49_05`OVlPt=4h100b10080 TTGO-LoRe_X-GatowNNN
20250330203047DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_00022e...t044h100b10080 TTGO-LoRa_WX-GatowNNN
20250330225147DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_0:/000g...t043h100b10090 TTGO-LoRa_WX-GatowNNN
20250330225714DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_00020E...t043h100b10090 TTGO-LoRaWk.GatowNNN
20250330230348DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_000o0p4g...t042h100b10090 TTG-LoRa_WX-GatowNNN