APRS Packet Errors for SV2BBO-15 (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
20251013090620SV2BBO-15>APLRG1,TCPIP*,qAC,T2PANAMA:!/9wkFTD{=_ G.../...g...t083h33b10207LoRa APRS WX Plateia
20251013092121SV2BBO-15>APLRG1,TCPIP*,qAC,T2PANAMA:!/9wkFTD{=_ G.../...g...t083h32b10207LoRa APRS WX Plateia
20251013100621SV2BBO-15>APLRG1,TCPIP*,qAC,T2PANAMA:!/9wkFTD{=_ G.../...g...t083h33b10206LoRa APRS WX Plateia
20251013102121SV2BBO-15>APLRG1,TCPIP*,qAC,T2PANAMA:!/9wkFTD{=_ G.../...g...t082h32b10205LoRa APRS WX Plateia
20251013120622SV2BBO-15>APLRG1,TCPIP*,qAC,T2PANAMA:!/9wkFTD{=_ G.../...g...t082h32b10199LoRa APRS WX Plateia
20251013122118SV2BBO-15>APLRG1,TCPIP*,qAC,T2BC:!/9wkFTD{=_ G.../...g...t082h32b10199LoRa APRS WX Plateia
20251013123618SV2BBO-15>APLRG1,TCPIP*,qAC,T2BC:!/9wkFTD{=_ G.../...g...t082h34b10198LoRa APRS WX Plateia
20251013125119SV2BBO-15>APLRG1,TCPIP*,qAC,T2BC:!/9wkFTD{=_ G.../...g...t083h35b10198LoRa APRS WX Plateia
20251013130619SV2BBO-15>APLRG1,TCPIP*,qAC,T2BC:!/9wkFTD{=_ G.../...g...t083h34b10197LoRa APRS WX Plateia