APRS Packet Errors for OE7BSH-97 (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
20260209132648OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=095/A=001982
20260209135703OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=086/A=001982
20260209142718OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=061/A=001982
20260209145736OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=061/A=001982
20260209152751OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=062/A=001982
20260209155806OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=081/A=001982
20260209162822OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=081/A=001982
20260209165837OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=090/A=001982
20260209172852OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=096/A=001982
20260209175907OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=094/A=001982
20260209182923OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=100/A=001982
20260209185938OE7BSH-97>APRSGW,TCPIP*,qAR,OE7BSH-97:!4717.65N/01134.98E#/B=090/A=001982