APRS Packet Errors for OK5TVR-5 (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
20260410165022OK5TVR-5>APRS,qAS,OK1RPL-15:!4947.38N/137$40E_135/001g003t041r000p0015P...h94b10122L11 WX-lora by OK5TVR DR:-121 DS:-20.25
20260410172023OK5TVR-5>APRS,qAS,OK1RPL-15:!4947XK61317.40E_135/000g000t041r000p0015P...h94b1011L#WX-lora by OK5TVR DR:-122 DS:-21.00
20260410180526OK5TVR-5>APRS,qAS,OK1PNK-10:!49$7.2(N/01317.40E_315/001g004t040r000p0015P...h97b10133L0 WX-lora by OK5TVR DS -18.75 RS -112
20260410205039OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_222/00 g001t035r000p0015P...h100b10148L0 WX-lora by OK5TVR DS -14.00 RS -115
20260410205039OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_222/00 g001t035r000p0015P...h100b10148L0 WX-lora by OK5TVR
20260410221517OK5TVR-5>APRS,TCPIP*,qAC,T2CZECH:!4947.38N/01317.40E_315/00 g002t035r000p0015P...h100b10147L0 WX-lora by OK5TVR
20260410221517OK5TVR-5>APRS,qAS,OK1PNK-10:!4947.38N/01317.40E_315/00 g002t035r000p0015P...h100b10147L0 WX-lora by OK5TVR DS -14.00 RS -115
20260410223017OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.44A#PEB
20260410224517OK5TVR-5>APRS,qAO,OK1CTR-10:!4947.38N/01317.40E_3 5?001g002t035r000p35R.>X#00b10147L0 WX-lora by OK5TVR