APRS Packet Errors for DB0FGB (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
20241226190854DB0FGB>APGE01,OK2ZAW-17*,qAO,OK1FWG-10:!5003.10N0:1151.18E&AP 144,800 & Lora 433,775MHz - Schneeberg DP_RSSI: -122 dBm DP_SNR: -18.25 dB
20241226194152DB0FGB>APGE01,OK2ZAW-17*,qAO,OK2ULQ-11:!5003.10N DP_R[A:%122 dBm DP_SNR: -22.25 dB
20241226194152DB0FGB>APGE01,OK2ZAW-17*,qAS,OL7M-10:!5003.10N DP_RSSI: -122 dBm DP_SNR: -22.25 dB DP_RSSI: -102 dBm DP_SNR: 9.50 dB
20241226194152DB0FGB>APGE01,OK2ZAW-17*,qAS,OK1CMJ-15:!5003.10N DP_RSSI: -122 dBm DP_SNR: 28.25 dB
20241226194243DB0FGB>APGE01,OK2ZAW-17*,qAO,OK1FWG-10:!5003.10N DP_RZ٪ D744 bBm DP_SNR: -22.25OK2JIB-10>APLRG1,OK2ZA-17*,qAO,OK1FWG-10:!L4vL0fa GLoRa APRS iGate DP_RSSI: -123 dBm DP_SNR: -13.50 dB
20241226202353DB0FGB>APGE01,OK2ZAW-17*,qAS,OK1TZL-1:!50090061151.18E&LoRa - 433,775MHz <> Schneeberg/Fichtelgeb. DP_RSSI: -121 dBm DP_SNR: -18.00 dB
20241226202554DB0FGB>APGE01,OK2ZAW-17*,qAS,OK1CMJ-15:!500;.10N00=51.18E&APRS 144,800 &@tg 433,775MHz - Schneeberg DP_RSSI: -122 dBm DP_SNR: -18.75 dB
20241226204754DB0FGB>APGE01,OK2ZAW-17*,qAO,OK1FWG-10:!5003.10N0PW157.18E&AR%14800 & Lora 433,775MHz - Schneeberg DP_RSSI: -122 dBm DP_SNR: -18.50 dB
20241226231049DB0FGB>APGE01,OK1CMJ-14*,qAO,OK1VP-10:!5003.10N001151-@FfE@ =/100 & Lora 433,775MHz - Schneeberg