APRS Packet Errors for DH1BUZ-12 (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
20250508071421DH1BUZ-12>APRS,DH1BQZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49_080/000g...t056h4fg10170 TTGO-LoR1R}Bw
20250508072305DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_0003:g$..t056h44b10170 TTGO-LoRa_WX-GatowNNN
20250508073401DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_000/:6P-G:<8x43b1017MNw)n)Ag_WX-o
20250508095038DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!52 -07M/01308.49E_000/000g...t067h32b10170 TTGO-LoR-GatowNNN
20250508103421DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49NNN,000g.t360h35b10160 TTGO-LoRa_WX-GatowNNN
20250508111447DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_0002Tc+HNP62h32"54q2TGh/G`_WX-GatowNNN
20250509023354DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!628.34N/01308.49E_000/000g...t07
20250509030219DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/30308=:E08_TC5BNFx Ei"]:V5_d%r]E
20250509055500DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49E_000y|-GUr(4Q0Q>6 TTO-LZa[XmCep+w
20250509061903DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49Ơ0/000g...t051h74b10180 TTGO-LoRa_WX-GatowNNN
20250509064054DH1BUZ-12>APRS,DH1BUZ-13*,qAO,DO0SDL-L4:!5228.34N/01308.49Ʃ00/000g...t054h64b10180 TTGO-LoRa_WX-GatowNNN