APRS Packet Errors for VE7GEL-1 (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
20190220073106VE7GEL-1>APAGW,SSI,WIDE2*,qAR,VA7DXH:=4835.57NVE7BSA>TXSYYS,VE7RNA-10*,WIDE2-1,qAR,VA7DXH:`34ul4&-"4*}TinyTrak3-IC02AT
20190220105117VE7GEL-1>APAGW,SSI,WIDE2*,qAR,VA7DXH:=4835.57NVA7RCA>WIDE2-1,qAR,VA7DXH:@201051z/5Xx&/O)I_!!bg000t033r000p028P000h98b10097wx report
20190220112112VE7GEL-1>APAGW,SSI,WIDE2*,qAR,VA7DXH:=4835.57NVE7NFW-1>APTW14,SSI,WIDE2*,qAR,VA7DXH:_02222245c024s000g000t035r000p000P000h..b.....tU2k
20190220113113VE7GEL-1>APAGW,SSI,WIDE2*,qAR,VA7DXH:=4835.57NVE7DYT-8>ID,qAR,VA7DXH:NANAIMO BPQ NODE (VE7DYT-8)