APRS Packet Errors for F4HUO-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
20260208164028F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny_ G.../...g...t072h40b09938LoRa APRS Digi
20260208171029F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny# GLoRa APRS Digi|!9$^$7"m!!!!|
20260208174030F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny_ G.../...g...t069h42b09945LoRa APRS Digi
20260208181030F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny# GLoRa APRS Digi|!:$`$7"m!!!!|
20260208184031F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny_ G.../...g...t071h42b09945LoRa APRS Digi
20260208191032F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny# GLoRa APRS Digi|!;$d$9"o!!!!|
20260208194032F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny_ G.../...g...t071h42b09947LoRa APRS Digi
20260208201033F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny# GLoRa APRS Digi|!<$g$:"p!!!!|
20260208204034F4HUO-10>APLRFD,TCPIP*,qAC,NINTH:!L5l%_O.ny_ G.../...g...t071h41b09946LoRa APRS Digi
20260208211027F4HUO-10>APLRFD,TCPIP*,qAC,EIGHTH:!L5l%_O.ny# GLoRa APRS Digi|%F$j$;"q!!!!|
20260208214028F4HUO-10>APLRFD,TCPIP*,qAC,FIFTH:!L5l%_O.ny_ G.../...g...t071h42b09948LoRa APRS Digi
20260208221028F4HUO-10>APLRFD,TCPIP*,qAC,FIFTH:!L5l%_O.ny# GLoRa APRS Digi|%G$l$;"q!!!!|