APRS Packet Errors for G4JBD-7 (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
20250915142124G4JBD-7>APLRT1,M0TAZ-2*,qAO,G4ERO-10:=/43@(NF:;_ !G.../...g...t066h54b10041
20250915151126G4JBD-7>APLRT1,M0TAZ-2*,qAO,M0VFC:=/43@,NF:9_ !G.../...g...t066h52b10054
20250915152126G4JBD-7>APLRT1,M0TAZ-2*,qAO,M0BLF-4:=/43@,NF:=_ !G.../...g...t066h53b10049
20250915155127G4JBD-7>APLRT1,M0TAZ-2*,qAO,M0BLF-4:=/43@(NF:4_ !G.../...g...t064h55b10045
20250915162128G4JBD-7>APLRT1,M0TAZ-2*,qAR,M1GEO-2:=/43@)NF:9_ !G.../...g...t064h56b10052
20250915163135G4JBD-7>APLRT1,M0TAZ-2*,qAR,G0RNI-15:=/43@)NF:6_ !G.../...g...t063h57b10053
20250915165130G4JBD-7>APLRT1,M0TAZ-2*,qAR,M1GEO-2:=/43@.NF:4_ !G.../...g...t062h58b10046