APRS Packet Errors for DB1NTO-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
20260209130000DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209131500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209141500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209143000DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209144500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209151500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209160000DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209161500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209170000DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209171500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209174500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209181500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209183000DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate
20260209184500DB1NTO-1>APPIC3,qAS,DB1NTO-2:!4927.60NR01055.36E&PicoAPRS RX iGate