APRS Packet Errors for OK0DBF-10 (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
20251215060141OK0DBF-10>APLRG1,OK2ZAW-17*,qAO,OE3YHC-11:!L5.&7$0, GLoRa AVQS iGATE Dolni Morava Batt=4.31V DP_RSSI: -115 dBm DP_SNR: 5.00
20251215060149OK0DBF-10>APLRG1,OK2ZAW-17*,qAO,OM3KUK-10:!|TOuPAmuC/
20251215102149OK0DBF-10>APLRG1,OK2ZAW-17*,qAO,OK2R-12:!9.&Re.Ti@ !LRaAPRS iGATE Dolni Morava Batt=4.34V DP_RSSI: -123 dBm DP_SNx*26.25`Fhʂ
20251215102153OK0DBF-10>APLRG1,OK2ZAW-17*,qAO,OE3YHC-11:!L5.&7Re.a Lra bRRS GATG*DlDk
20251215174140OK0DBF-10>APLRG1,OK2AW-17*,qAO,OK2ULQ-11:! (pb͈ɶWm[1S$mCAEE0To
20251215224138OK0DBF-10>APLRG1,OK2ZAW-17*,qAO,OK2AF-10:!L5.&7.PlM?ӳPk[:삡H!Q`1x.ǥuDH>)VIm#.2|.wk=0!1nEV:
20251216050150OK0DBF-10>xYEG1,OK2ZAW-17*,qAO,OE5XIM-11:!L7(`Pb*D|lQ` A@R5@oGGTE Dolni Morava Batt=4.32V DP_RSSI: -123 dBm DP_SNR: -14.00 dB