APRS Packet Errors for 2E0LSR-6 (last 24 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
202504011603222E0LSR-6>APLRT1,WIDE1-1,qAR,2E0LSR-10:!/3pRWNo%H_!!Q.../...g...t084r...p...P...h28b10255
202504011623312E0LSR-6>APLRT1,WIDE1-1,qAR,MB7UKT-10:!/3ig?Nn#u_:Q.../...g...t092r...p...P...h20b10299
202504020657242E0LSR-6>APLRT1,WIDE1-1,qAR,MB7UKT-10:!/3lL/NoC$_7-Q.../...g...t053r...p...P...h38b10282
202504020707282E0LSR-6>APLRT1,WIDE1-1,qAR,2E0LSR-10:!/3o]hNnB\_8$Q.../...g...t059r...p...P...h38b10288
202504020717322E0LSR-6>APLRT1,WIDE1-1,qAR,2E0LSR-10:!/3pPHNo%*_7XQ.../...g...t065r...p...P...h37b10282