APRS Packet Errors for G4TVP-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
20250509104524G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:PSNciG_ !Q.../...g...t074h40b10225Gas: 262.09KohmsTesting this LORA APRS tracker|(0%O|
20250509105533G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:OINchX_ )Q.../...g...t074h39b10313Gas: 268.50Kohms
20250509110656G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:N6Nci=_ !Q.../...g...t074h38b10211Gas: 282.07Kohms
20250509110754G4TVP-8>APLRT1,MB7UOH-10*,qAO,M0IDA-10:!/4:N6Nci=_ !Q.../...g...t074h38b10211Gas: 282.07Kohms
20250509113935G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:P%Nchb_ !Q.../...g...t074h38b10216Gas: 298.70Kohms
20250509115018G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:NaNch(_ jQ.../...g...t074h37b10240Gas: 290.79Kohms
20250509115059G4TVP-8>APLRT1,MB7UOH-10*,qAO,M0IDA-10:!/4:NaNch(_ jQ.../...g...t074h37b10240Gas: 290.79Kohms
20250509142620G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:OQNci/_ !Q.../...g...t073h36b10161Gas: 322.38Kohms
20250509143855G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:OaNchH_ nQ.../...g...t074h42b10219Gas: 288.24Kohms
20250509160648G4TVP-8>APLRT1,WIDE1-1,qAR,MB7UOH-10:!/4:P=NchX_ HQ.../...g...t075h40b10217Gas: 210.50Kohms
20250509160732G4TVP-8>APLRT1,MB7UOH-10*,qAO,M0IDA-10:!/4:P=NchX_ HQ.../...g...t075h40b10217Gas: 210.50Kohms