APRS Packet Errors for 9W2JEK-8 (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
202602090016589W2JEK-8>APOTC1,WIDE1-1,WIDE2-2,qAR,9W2JEK-1:!0200.58N/10318.79E>077/035/A=-00000 13.9V 19C Jerangkong de kandang Langau
202602090017129W2JEK-8>APOTC1,WIDE1-1,qAR,9W2JEK-1:!0200.60N/10318.88E>078/026/A=-00000 13.8V 19C Jerangkong de kandang Langau
202602090017399W2JEK-8>APOTC1,WIDE1-1,qAR,9W2JEK-1:!0200.70N/10318.92E>045/015/A=-00000 13.8V 19C Jerangkong de kandang Langau
202602090019079W2JEK-8>APOTC1,9M4RJN-3,WIDE1*,WIDE2-2,qAS,9W2DCW-3:!0200.93N/10319.13E>047/019/A=000215 13.8V 21C Jerangkong de kandang Langau
202602090020079W2JEK-8>APOTC1,WIDE1-1,qAR,9W2JEK-1:!0200.94N/10319.17E>030/000/A=000213 12.7V 21C Jerangkong de kandang Langau
202602090022079W2JEK-8>APOTC1,WIDE1-1,WIDE2-2,qAR,9W2JEK-1:!0201.33N/10318.73E>306/021/A=000137 13.8V 23C Jerangkong de kandang Langau
202602090022529W2JEK-8>APOTC1,WIDE1-1,qAR,9W2JEK-1:!0201.36N/10318.69E>275/009/A=000185 13.7V 23C Jerangkong de kandang Langau
202602090023279W2JEK-8>APOTC1,WIDE1-1,WIDE2-2,qAR,9W2JEK-1:!0201.30N/10318.81E>099/013/A=000154 13.7V 23C Jerangkong de kandang Langau
202602090024359W2JEK-8>APOTC1,WIDE1-1,qAR,9W2JEK-1:!0201.45N/10318.98E>069/009/A=000214 13.8V 23C Jerangkong de kandang Langau