APRS Packet Errors for OE4ENU-10 (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
20260208132447OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208135502OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208142517OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208145532OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208152543OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208155601OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208162616OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208165632OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208172652OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208175707OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208182723OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208185738OE4ENU-10>APRSGW,TCPIP*,qAR,OE4ENU-10:!4745.19N/01632.51E-Meshcom Gw/B=100/A=000902
20260208185741OE4ENU-10>APLT00-1,WIDE1-1,qAO,OE4DNS-2:=/6AA"R^Jw- P[