APRS Packet Errors for VE7MIS (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
20260209155219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@155218h4908.37N/12218.09Wo146.460 MARES Net Monday 8pm
20260209162219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@162218h4908.37N/12218.09Wo
20260209165219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@165218h4908.37N/12218.09Wo146.460 MARES Net Monday 8pm
20260209172219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@172218h4908.37N/12218.09Wo
20260209175219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@175218h4908.37N/12218.09Wo146.460 MARES Net Monday 8pm
20260209182219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@182218h4908.37N/12218.09Wo
20260209185219VE7MIS>APWW11,TCPIP*,qAC,T2PR:@185218h4908.37N/12218.09Wo146.460 MARES Net Monday 8pm
20260209192220VE7MIS>APWW11,TCPIP*,qAC,T2PR:@192219h4908.37N/12218.09Wo
20260209195220VE7MIS>APWW11,TCPIP*,qAC,T2PR:@195219h4908.37N/12218.09Wo146.460 MARES Net Monday 8pm
20260209202220VE7MIS>APWW11,TCPIP*,qAC,T2PR:@202219h4908.37N/12218.09Wo
20260209205220VE7MIS>APWW11,TCPIP*,qAC,T2PR:@205219h4908.37N/12218.09Wo146.460 MARES Net Monday 8pm
20260209212220VE7MIS>APWW11,TCPIP*,qAC,T2PR:@212219h4908.37N/12218.09Wo