APRS Packet Errors for LW3HBV-2 (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
20250211083235LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAR,LU1HD-1:!305.50S/06429.11W#LW3HBV-2 Ant:Omni 1/2 (por LU1HES) 1670msnm 4W
20250211085048LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAO,LU4HH:!3055.50S/0W#LW3HBV-2 Digi Los Cocos FF79SB (sitio por LW5HDJ)
20250211090903LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAR,LU1HD-1:!350S/06429.11W#LW3HBV-2 Ant:Omni 1/2 (por LU1HES) 1670msnm 4W
20250211092922LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAR,LU1HD-1:!305.50S/06429.11W#LW3HBV-2 Digi Los Cocos 144.390 RX/TX Res.508/18
20250211101801LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAO,LU4HH:!3055.29.11W#LW3HBV-2 Digi Los Cocos 144.390 RX/TX Res.508/18
20250211102202LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAR,LU1HD-1:!055.50S/06429.11W#LW3HBV-2 Digi Los Cocos FF79SB (sitio por LW5HDJ)
20250211104651LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAO,LU4HH:!3055.50S/064LW3HBV-2 Ant:Omni 1/2 (por LU1HES) 1670msnm 4W
20250211110314LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAO,LU4HH:!3055.50S11W#LW3HBV-2 Digi Los Cocos FF79SB (sitio por LW5HDJ)
20250211130517LW3HBV-2>APBK20,LU4HH-10,WIDE1,LU4HH-11*,WIDE2-1,qAR,LU1HD-1:!055.50S/06429.11W#LW3HBV-2 Digi Los Cocos FF79SB (sitio por LW5HDJ)