APRS Packet Errors for OK1ALX-11 (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
20240420041327OK1ALX-11>APLT00-1,OK2ZAW-17*,qAO,OK2CME-12:!4956.8G/01524.57E>3294`/D=000738LoRa tracker QRO.cz - _Bat.: 4.50V Cur.: -3mA 0DPVS0 -122`gĎ_S"df)]K%w!
20240420041737OK1ALX-11>APLT00-1,OK2ZAW-17*,qAO,OK2CME-12:!49e8.56N/0152.7M 7:39/A=00p7rꡄ(_Bat.: 4.50V -S$0(: DP_^ Q`kafAK NMp/?HW
20240420044351OK1ALX-11>APLT00-1,OK2ZAW-17*,qAR,OK0BRQ-12:!4958.98N/0152&?>360/000/A=0006>9LoRa tracker .kz - _AbG: 4.50V - CurHZ -4mA DP_RSSI: -120 dBm DP_SNR: -0.50 dB !wTr!
20240420045859OK1ALX-11>APLT00-1,OK2ZAW-17*,qAR,OK0BRQ-12:!4958O6B8 =967016/A=000867 - _Bat.: 4.50V - Cur.: -4mA DP_RSSI: -122 dBm DP_SNR: -13.50 dB !w-.!
20240420045921OK1ALX-11>APLT00-1,OK2ZAW-17*,qAR,OK0BRQ-12:!4953.79N/89=7.50E>133/018/A=000889 - _Bat.: 4.50V - Cur.: -3m _RSUI: -11,ΩSPM7|DsHve_x