APRS Packet Errors for VE3TBI (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
20260208145004VE3TBI>APIN21,WIDE1-1,WIDE2-1,qAR,VA3RAW-3:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208152006VE3TBI>APIN21,VE3OMP,WIDE1*,WIDE2-1,qAR,VE3XII-12:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208155004VE3TBI>APIN21,WIDE1-1,WIDE2-1,qAR,VA3RAW-3:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208162005VE3TBI>APIN21,VE3OMP,WIDE1*,WIDE2-1,qAR,VE3XII-12:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208165004VE3TBI>APIN21,WIDE1-1,WIDE2-1,qAR,VA3RAW-3:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208172007VE3TBI>APIN21,VE3OMP,WIDE1*,WIDE2-1,qAR,VE3XII-12:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208175007VE3TBI>APIN21,VE3OMP,WIDE1*,WIDE2-1,qAR,VE3XII-12:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208182004VE3TBI>APIN21,WIDE1-1,WIDE2-1,qAR,VA3RAW-3:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208185008VE3TBI>APIN21,VE3OMP,WIDE1,CASCTY,WIDE2*,qAR,METMOR:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208192007VE3TBI>APIN21,VE3OMP,WIDE1,CASCTY,WIDE2*,qAR,METMOR:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208195008VE3TBI>APIN21,VE3OMP,WIDE1,CASCTY,WIDE2*,qAR,JAMTWP:!4300.68N/08222.91Wy73 from Sarnia Ont
20260208202005VE3TBI>APIN21,WIDE1-1,WIDE2-1,qAR,VA3RAW-3:!4300.68N/08222.91Wy73 from Sarnia Ont