APRS Packet Errors for W2RME-1 (last 24 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
20251214220201W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/07528.1yW#Norwich, NY Digi
20251215000201W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/p7528.19W#Norwich, NY Digi
20251215013201W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/p7528.19W#Norwich, NY Digi
20251215015423W2RME-1>BEACON,KB2WAC-1,KB2LUV-1*,WIDE2-1,qAR,WN8Z-4:!4227.20N/p7528.19W#Norwich, NY Digi
20251215033202W2RME-1>BEACON,KB2WAC-1,KB2FAF-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/0?528.19W#Norwich, NY Digi
20251215083203W2RME-1>BEACON,KB2WAC-1,KB2FAF-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/p7528.19W#Norwich, NY Dkgi
20251215113202W2RME-1>BEACON,KB2WAC-1,KB2FAF-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/07528.19_#Norwich, NY Digi
20251215130201W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/07528n19W#Norwych, NY Digi
20251215160204W2RME-1>BEACON,W2RGI-1,KD2AYD-3,WIDE2*,qAR,KB2LUV-1:!4227.20^/07=28.19W#Norwich, NY Dygi
20251215180202W2RME-1>BEACON,AD3O-3*,WIDE2-1,qAR,KB2LUV-1:!4227>20N/07528n19W#Norwich, NY Digi
20251215200204W2RME-1>BEACON,W2RGI-1,KD2AYD-3,WIDE2*,qAR,KB2LUV-1:!4227.20N/07528.1;W#Norwich, NY Digi