APRS Packet Errors for SP2NBH-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
20260707070452	SP2NBH-7>APLRT1,WIDE1-1,qAR,SQ2WSZ-1:=/3$0vS1pC_>sQ.../...g...t083h50
20260707071453	SP2NBH-7>APLRT1,WIDE1-1,qAR,SQ2WSZ-1:=/3$0VS1pW_>uQ.../...g...t084h49
20260707072453	SP2NBH-7>APLRT1,WIDE1-1,qAR,SQ2WSZ-1:=/3$17S1p>_>zQ.../...g...t086h49 Bat=3.91V 75%
20260707073453	SP2NBH-7>APLRT1,WIDE1-1,qAR,SQ2WSZ-1:=/3$0]S1p`_?+Q.../...g...t087h48
20260707074454	SP2NBH-7>APLRT1,WIDE1-1,qAR,SQ2WSZ-1:=/3$0bS1pW_?0Q.../...g...t087h46
20260707075454	SP2NBH-7>APLRT1,WIDE1-1,qAR,SQ2WSZ-1:=/3$0lS1p>_?4Q.../...g...t088h45