APRS Packet Errors for OK1VIG-1 (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
20261024084044OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37Nã013)6.T3EIPHG2130 13.2V
20261024091344OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37N#0131.43EIPHG2130 13.2V
20261024093544OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37N#0136.43EIPHG2130 13.3V
20261024104544OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.3;N#01316.43EIPHG2130 13.4V
20261024133146OK1VIG-1>APET51,OK0BR-1*,qAR,OK1RPL-1:!4949.37N#01316-43EIPHG2130 13.3VÈ
20261024181756OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37N#0131
20261024181956OK1VIG-1>APET51,OK0BR-1*,qAR,OK0BPT-1:!4949.37N#0131
20261024182457OK1VIG-1>APET51,OK0BR-1*,qAR,OE3EMC-10:!4949(37N#01316.43EIPHG2130 13.1V
20261024185356OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37N#01316"43EIPHG2130 13.1V
20261024192757OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.3·¯˜˜™š™¢$(¤#™˜˜—+
20261024194357OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37N#0Q316.43EIPHG2130 13.1V
20261024203357OK1VIG-1>APET51,OK0BR-1*,qAR,OK0BPT-1:!4949.37N#01316.43E
20261024213857OK1VIG-1>APET51,OK0BR-1*,qAR,OE5XIM-10:!4949.37N#01316