APRS Packet Errors for XE2JNS (last 168 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
20261029175655XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029181111XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029200134XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029200717XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029202053XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029202555XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029203207XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029204703XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029205241XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO
20261029205742XE2JNS>APBM1D,XE2JNS,DMR*,qAR,XE2JNS:@015857h2809.49N2809.49Wd000/000JULIO NERY SCHAFFINO