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
20260306050252W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/p7528.19W#Norwich, NY Digi
20260306050257W2RME-1>BEACON,KD2AYD-3,WN8Z-4,WIDE2*,qAR,KB2LUV-1:!4227.20N/07528n19W#Norwich, NY Digi
20260306063253W2RME-1>BEACON,AD3O-3,KC2ANT-1,WIDE2*,qAR,KB2LUV-1:!4227.20N/p7528.19W#Nor÷ich, NY Digi
20260306093255W2RME-1>BEACON,KD2AYD-3,WN8Z-4,WIDE2*,qAR,KB2LUV-1:!422?.20N/07528.19W#Norwich, NY Digi
20260306130257W2RME-1>BEACON,KD2AYD-3,WN8Z-4,WIDE2*,qAR,KB2LUV-1:!4227.20^/07528.19W#Norwich,`NY Digi
20260306133301W2RME-1>BEACON,KD2AYD-3,WN8Z-4,WIDE2*,qAR,KB2LUV-1:!422?.20N/07528.19W#Norwich, NY Digi
20260307000254W2RME-1>BEACON,AD3O-3,KC2ANT-1,WIDE2*,qAR,KB2LUV-1:!4227n20N/07528.19W#Norwich, NY Digi
20260307010252W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.2pN/07528.19W#Norwich, NY Digi
20260307030252W2RME-1>BEACON,KB2WAC-1*,WIDE2-1,qAR,KB2LUV-1:!4227.20N/07528n19W#Norwich, NY Digi
20260307035200W2RME-1>BEACON,KB2WAC-1,KB2LUV-1*,WIDE2-1,qAR,KB2WAC-1:!4227.20N/07528n19W#Norwich, NY Digi