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
20261024013323DH1BUZ-12>APRS,DH1BUZ-15*,qAS,DH1BUZ-14:!5228.34N/01308.49u_Y2&000b.050h95b10010 TTGO-LoRa_WX-Gatow
20261024013354DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34N/01308.49u_Y2&000b.050h95b10010 TTGO-LoRa_WX-Gatow
20261024114150DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!52rsn,-2Q%аd7Wy<w3m]R7zh[#hs B?9Z|FW5
20261024120317DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34nMZoR"Y}ƞwKnUoNav̧hA%VyS
20261024120351DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34nMZoR"Y}ƞwKnUoNav̧hA%VyS
20261024120918DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34N/0130Ae"&73m!?u /<Sqd3
20261024124949DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34N/01308.49E_000R6NUUk|׊^J
20261024184155DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34N/013<1e&d2 SHxXuw*"m4 fW0 )hHeS`
20261024184228DH1BUZ-12>APRS,DH1BUZ-14*,qAS,DH1BUZ-15:!5228.34N/013<1e&d2 SHxXuw*"m4 fW0 )hHeS`