APRS Packet Errors for OE1KDA-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
20260209093736OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209100751OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209103806OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209110821OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209113840OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209120855OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209123910OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209130927OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209133942OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209144012OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623
20260209151027OE1KDA-13>APRSGW,TCPIP*,qAR,OE1KDA-13:!4808.23N/01620.99E#GW 868 Wien 23#Krzysztof/B=100/A=000623