APRS Packet Errors for HB9FRR-98 (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
20260209121019HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209124034HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209131049HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209134104HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209141120HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209144135HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209151150HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209154205HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209161220HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209164235HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209171250HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650
20260209174306HB9FRR-98>APRSGW,TCPIP*,qAR,HB9FRR-98:!4703.26N/00832.91E#/B=100/A=001650