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
20260928065605OK5TVR-5>APRS,OK1JRA-20*,qAS,OK1RPL-15:!4<47.38N/01317.40E_222/000g101t050r000L037P000h=a0184 WX by OK5TVR DR:-117 DS:4.00
20260928065605OK5TVR-5>APRS,OK1JRA-20*,qAR,OK4MD-12:!4<47.38N/01317.40E_222/000g101t050r000L037P000h=a0184 WX by OK5TVR
20260928082601OK5TVR-5>APRS,WIDE1-1,qAO,OK1VP-10:!4947.38N/01317.40E_22²/001o006t059r000L086P000h66b10176 WX by OK5TVR
20260928085601OK5TVR-5>APRS,WIDE1-1,qAO,OK1VP-10:!4947.38N/01317.40E_222/0e1g005t062r000L105P000h6“b;0173 WX by OK5TVR
20260928101101OK5TVR-5>APRS,WIDE1-1,qAO,OK1VP-10:!4947.38N/01317.40E_27°§0¸2o(°üyð6=òô40L158P000h50b10164 WX by OK5TVR