APRS Packet Errors for OK1JRA-6 (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
20260402193236OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943;G01308.73E_010/002g003t043h48b10152r000_B4.10V SNR=-19dB RSSI=-90db
20260402193742OK1JRA-6>APRS,OK0BR-12*,qAS,OK1PNK-10:!4943.12N/`a3e8+73E_004/002g002t043h48b10153r000_B4.10V DS -10.50 RS -113
20260402194754OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/01308.7028/001g002t042h48b10154r000_B4.10V SNR=-20dB RSSI=-91db
20260402205414OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/0qsp8.73E_310/001g002t040h57b10158r000_B4.08V SNR=-20dB RSSI=-92db
20260402211439OK1JRA-6>APRS,OK0BR-12*,qAS,OK1PNK-10:!4943.12N/013e=+73E_170/001g001t038h59b10160r000_B4.08V DS -12.50 RS -111
20260402222604OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.12N/0 r x+73E_346/001g002t034h63b10162r000_B4.08V SNR=-20dB RSSI=-90db
20260402232719OK1JRA-6>APRS,OK1JRA-15*,qAO,OK1CTR-10:!797.;W .
20260402234742OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943.aN/0.73E_335/000g001t032h67b10162r00_B4.05V SNR=-21dB RSSI=-91db
20260402235248OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!4943=;G51308.73E_355/000g000t031h68b10162r002_B4.56 SNR=-21dB RSSI=-91db
20260403002325OK1JRA-6>APRS,OK0BR-12*,qAS,OK1BIL-2:!49430׷1308.73E_045/000g000t030h67b10161r000_B4.05V SNR=-20dB RSSI=-89db