APRS Packet Errors for VA3TJS (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
20260208170604VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/170557h4326.74N/08102.31W>031/049/Tim from Milverton
20260208170734VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/170722h4327.62N/08101.73W>031/041/Tim from Milverton
20260208170754VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/170749h4327.91N/08101.48W>030/047/Tim from Milverton
20260208171104VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/171056h4329.89N/08059.86W>020/048/Tim from Milverton
20260208171644VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/171639h4332.15N/08056.72W>027/044/Tim from Milverton
20260208172134VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/172130h4333.62N/08055.12W>185/000/Tim from Milverton
20260208172624VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/172617h4333.62N/08055.12W>185/000/Tim from Milverton
20260208173144VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/173132h4333.63N/08055.12W>185/002/Tim from Milverton
20260208173304VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/173132h4333.63N/08055.12W>185/002/Tim from Milverton
20260208173414VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/173132h4333.63N/08055.12W>185/002/Tim from Milverton
20260208173604VA3TJS>API282,DSTAR*,qAR,VE3NMN-C:/173132h4333.63N/08055.12W>185/002/Tim from Milverton