APRS Packet Errors for VEDAN (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
20260208145531VEDAN>APOT30,WIDE2-2,qAR,DRMT39:!5132.27N/12326.31W# 13.3V 38C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208152737VEDAN>APOT30,WIDE2-2,qAR,DRMT39:!5132.27N/12326.31W# 13.3V 38C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208155944VEDAN>APOT30,PUNTZI,VE7SCQ,WIDE2*,qAR,DRMT39:!5132.27N/12326.31W# 13.5V 38C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208163134VEDAN>APOT30,SMOKEY,SPUD,WIDE2*,qAR,DRMT39:!5132.27N/12326.31W# 13.5V 38C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208170334VEDAN>APOT30,WIDE2-2,qAR,DRMT39:!5132.27N/12326.31W# 12.5V 38C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208173513VEDAN>APOT30,SPUD*,WIDE2-1,qAR,DRMT39:!5132.27N/12326.31W# 12.4V 38C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208180735VEDAN>APOT30,WIDE2-2,qAR,DRMT39:!5132.27N/12326.31W# 13.4V 42C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208183929VEDAN>APOT30,WIDE2-2,qAR,DRMT39:!5132.27N/12326.31W# 13.7V 41C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2
20260208191218VEDAN>APOT30,WIDE2-2,qAR,DRMT39:!5132.27N/12326.31W# 14.1V 43C VA7TRU VEDAN Rx 146.800 Tx 146.200 CTCSS 162.2