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
202602091046099W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.93V
202602091116099W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091146099W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091216109W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091246109W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091316109W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091346119W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.93V
202602091416119W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091446119W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091516119W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091546119W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.94V
202602091616099W2BWS>APLRG1,TCPIP*,qAC,MYAPRS:!LLoOEh3BEa GKg Tengah Gombak - Lora 433.400Mhz Batt=3.93V