APRS Packet Errors for W4EJW-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
20250913135341W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913135413W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913135458W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913135652W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913175727W4EJW-1>API710,DSTAR*,qAR,W4LCO-C:!2635.36N/08150.65_-/A=000015
20250913175826W4EJW-1>API710,DSTAR*,qAR,W4LCO-C:!2635.36N/08150.65_-/A=000015
20250913180144W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913191217W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913191251W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913191335W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913191448W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913191520W4EJW-1>API710,DSTAR*,qAS,KD8DXQ-G:!2635.36N/08150.65_-/A=000015
20250913204246W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913220503W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913222905W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015
20250913223224W4EJW-1>API710,DSTAR*,qAR,W4LCO-B:!2635.36N/08150.65_-/A=000015