APRS Packet Errors for EA2CW-13 (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
20260223074719EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL008 Lux:893_WX_APRS_LoRa
20260223080254EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL011 Lux:1157_WX_APRS_LoRa
20260223084935EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL013 Lux:1341_WX_APRS_LoRa
20260223092045EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL013 Lux:1383_WX_APRS_LoRa
20260223093620EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL013 Lux:1388_WX_APRS_LoRa
20260223105410EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL014 Lux:1472_WX_APRS_LoRa
20260223110946EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL014 Lux:1482_WX_APRS_LoRa
20260223112522EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL014 Lux:1489_WX_APRS_LoRa
20260223114058EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL014 Lux:1496_WX_APRS_LoRa