APRS Packet Errors for OK1FET-16 (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
20251215123454OK1FET-16>APRS,OK0BR-12*,qAR,DH4NBB-16:!5000N13(0215:+Z225/000g000t044h81b10739BA55
20251215124440OK1FET-16>APRS,OK0BR-12,DB0FGB*,qAS,DB0FGB:!5000.13N83.71E_225/000g000t044h81b1
20251215125429OK1FET-16>APRS,OK0BR-12*,qAO,OK1CPR-12:!50eF;$]ʑW s_ǢrKJQ9Ay}
20251215140740OK1FET-16>APRS,OK0BR-12*,qAS,OK1RPL-15:!53 DR:-120 DS:-12.50
20251215160450OK1FET-16>APRS,OK0BR-12*,qAR,OK4MD-13:!5000.13N/01259.71E_225/00!w 10x04?h78b10731_BATT=3"95V
20251215162915OK1FET-16>APRS,OK0BR-12*,qAR,OK4MD-13:!5000.13NTa9.71E_225/`00g505t046h78b10732_BATT=3.54V
20251215170325OK1FET-16>APRS,OK0BR-12*,qAR,OK4MD-13:!500%01259.71E_2>5/000g000t043h78b10733_BATT=3.55V
20251215173244OK1FET-16>APRS,OK0BR-12*,qAR,OK4MD-13:!5000.13N/0125:.71E_225/00e020t043h78b!dwwe_BATT=3.54V
20251215182132OK1FET-16>APRS,OK0BR-12*,qAR,OK4MD-13:!5000.13N/0125y.53AfD`Ph:PPth$һ$|