APRS Packet Errors for OE1GNR-12 (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
20260208134245OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208141300OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=091/A=000764
20260208144313OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208151328OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=092/A=000764
20260208154343OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208161402OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=088/A=000764
20260208164417OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208171429OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208174444OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=092/A=000764
20260208181459OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208184516OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=100/A=000764
20260208191532OE1GNR-12>APRSGW,TCPIP*,qAR,OE1GNR-12:!4811.29NG01622.06E#meshcom 4.0/B=092/A=000764