APRS Packet Errors for PU5NFH-10 (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
20260209092403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209095403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209102403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209105403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209112403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209115403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209122403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209125403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209132403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209135403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209142403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER
20260209145403PU5NFH-10>APBK15,TCPIP*,qAC,T2BRAZIL:!2530.15S/04918.26W& IGATE 1a REER