APRS Packet Errors for SR8MBR-2 (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
20250420151541SR8MBR-2>APRX29,SP8AA-1*,QA7N1,qAR,SR8MBR-1:;439.2875RZE111z5003.72N/02157.29Er439.2875MHz c071 -760 R30k SR8RZE Rzeszów
20250420151545SR8MBR-2>APRX29,SP8AA-1,SQ8RZE-1*,qAR,SQ8IJR-10:;439.250MZ111111z5001.10N/02241.06Er439.250MHz c67 -760 R30k SR8JR Jarosław
20250420154004SR8MBR-2>APRX29,SP8AA-1*,QA7N1,qAR,SR8MBR-1:;439.2875RZE111z5003.72N/02157.29Er439.2875MHz c071 -760 R30k SR8RZE Rzeszów
20250420161905SR8MBR-2>APRX29,SP8AA-1*,QA8N2,qAR,SR8MBR-1:;439.2875RZE111z5003.72N/02157.29Er439.2875MHz c071 -760 R30k SR8RZE Rzeszów
20250420194329SR8MBR-2>APRX29,SQ8PDY-4,WIDE1*,QA9N3,qAR,SR8MBR-1:;439.2875RZE111z5003.72N/02157.29Er439.2875MHz c071 -760 R30k SR8RZE Rzeszów