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
20260224072613	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL005 Lux:617_WX_APRS_LoRa
20260224074149	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL009 Lux:998_WX_APRS_LoRa
20260224075725	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL014 Lux:1513_WX_APRS_LoRa
20260224081301	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2AFZ-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL019 Lux:1992_WX_APRS_LoRa
20260224082837	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL038 Lux:3997_WX_APRS_LoRa
20260224084413	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL029 Lux:3085_WX_APRS_LoRa
20260224085949	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL029 Lux:3005_WX_APRS_LoRa
20260224100212	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL034 Lux:3523_WX_APRS_LoRa
20260224110436	EA2CW-13>APLWX1,WIDE1-1,qAR,EA2CW-10:!4315.56N/00255.60W_.../...g...tnanr...p...P...hnanbnanL045 Lux:4730_WX_APRS_LoRa