APRS Packet Errors for SR8BCH-1 (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
20251206213010SR8BCH-1>APNU19,WIDE2-1,qAR,SR8SDI:!5107.66NS02328.48#EL-684484 433.575MHz
20251206220010SR8BCH-1>APNU19,WIDE2-1,qAR,SR8SDI:!5107.66NS02328.48#EL-684484 433.575MHz
20251206223012SR8BCH-1>APNU19,WIDE2-1,qAR,SR8SDI:!5107.66NS02328.48#EL-684484 433.575MHz
20251206230012SR8BCH-1>APNU19,WIDE2-1,qAR,SR8NL:!5107.66NS02328.48#EL-684484 433.575MHz
20251206233014SR8BCH-1>APNU19,WIDE2-1,qAR,SR8SDI:!5107.66NS02328.48#EL-684484 433.575MHz
20251207000014SR8BCH-1>APNU19,WIDE2-1,qAR,SR8NL:!5107.66NS02328.48#EL-684484 433.575MHz
20251207003016SR8BCH-1>APNU19,WIDE2-1,qAR,SR8NL:!5107.66NS02328.48#EL-684484 433.575MHz
20251207010016SR8BCH-1>APNU19,WIDE2-1,qAR,SR8NL:!5107.66NS02328.48#EL-684484 433.575MHz
20251207013017SR8BCH-1>APNU19,WIDE2-1,qAR,SR8SDI:!5107.66NS02328.48#EL-684484 433.575MHz
20251207020019SR8BCH-1>APNU19,WIDE2-1,qAR,SR8NL:!5107.66NS02328.48#EL-684484 433.575MHz