APRS Packet Errors for OK0BR-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
20261024043929OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50NL21349.10"PMC41:0 DIGI_LoRA by O
20261024043929OK0BR-10>APZ023,qAS,OK1PNK-10:!4939.50NL0qc!9>00E%`HG01000 DIGI_LoRA by OK5TVR AP DS -14.50 RS -115
20261024053931OK0BR-10>APZ023,qAS,OK1RPL-15:!4939.50jXo
20261024093944OK0BR-10>APZ023,qAS,OK1JRA-16:!4939.50NL01c49.10E&PHG01000 DIGI_LoRA by OK5TVR AP DS -17.50 RS -91
20261024113950OK0BR-10>APZ023,qAS,OK1BIL-2:!499.50NL0139.1E%rIG332UH_Je`dp I3n(G!AP SNR=-23dB RSSI=-90db
20261024135957OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50I`4cqFW9^srv BI!)YLjWTE
20261024143959OK0BR-10>APZ023,qAR,OK4MD-13:!499.50NL01349.10EP
20261024180009OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50Nl369.10E&PHG010 IK_Lo[)by OK5TVR A
20261024190012OK0BR-10>APZ023,qAS,OK1JRA-16:!4939.50NL013$)>! D&PHG01000 DIGI_LoRA by OK5TVR AP DS -18.50 RS -91
20261024232025OK0BR-10>APZ023,qAR,OK4MD-13:!4939.50^L1134Y(WVO&PHG01000 tztzeRdI*M5TFC AP
20261025024035OK0BR-10>APZ023,qAS,OK1BIL-2:!4939.50O:0>?n14E&PHG||MWi_,ibA b9$OK_W BV SNR=-22dB RSSI=-105db
20261025032037OK0BR-10>APZ023,qAS,OK1BIL-2:!4939.50NL01349.10fPH41PZ0IG_LoA,bi OKVVP P SNR=-21dB RSSI=-90db