APRS Packet Errors for 9W2BWS (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
202602081316069W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=4.00V
202602081346069W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=4.00V
202602081416079W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.99V
202602081446089W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.99V
202602081516089W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.99V
202602081546099W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.99V
202602081616079W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.98V
202602081646079W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.97V
202602081716079W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.97V
202602081746089W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.97V
202602081816089W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.97V
202602081846089W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.95V