APRS Packet Errors for YU1BO (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
20260209145619	YU1BO>APRS,TCPIP*,qAC,SECOND:/091456z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209152618	YU1BO>APRS,TCPIP*,qAC,FIRST:/091526z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209155618	YU1BO>APRS,TCPIP*,qAC,FIRST:/091556z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209162619	YU1BO>APRS,TCPIP*,qAC,FIRST:/091626z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209165619	YU1BO>APRS,TCPIP*,qAC,SEVENTH:/091656z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209172619	YU1BO>APRS,TCPIP*,qAC,FIRST:/091726z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209175619	YU1BO>APRS,TCPIP*,qAC,FIFTH:/091756z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209182619	YU1BO>APRS,TCPIP*,qAC,THIRD:/091826z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209185619	YU1BO>APRS,TCPIP*,qAC,FOURTH:/091856z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209192619	YU1BO>APRS,TCPIP*,qAC,FOURTH:/091926z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209195619	YU1BO>APRS,TCPIP*,qAC,FOURTH:/091956z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR
20260209202619	YU1BO>APRS,TCPIP*,qAC,NINTH:/092026z4449.06N/02024.33E-Nikola - SU20 & SU20 DMR