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
20251013210621SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t076h38b10207LoRa APRS WX Plateia
20251013212121SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t076h39b10206LoRa APRS WX Plateia
20251013213621SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t075h40b10206LoRa APRS WX Plateia
20251013220623SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t074h41b10205LoRa APRS WX Plateia
20251013230623SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t072h42b10206LoRa APRS WX Plateia
20251013232123SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t072h42b10206LoRa APRS WX Plateia
20251013233623SV2BBO-15>APLRG1,TCPIP*,qAC,T2PERTH:!/9wkFTD{=_ G.../...g...t071h42b10205LoRa APRS WX Plateia