APRS Packet Errors for OE3OEK-11 (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
20260208134455OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=100/A=001588
20260208141510OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=079/A=001588
20260208144525OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=091/A=001588
20260208151541OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=098/A=001588
20260208154556OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=089/A=001588
20260208161607OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=080/A=001588
20260208164622OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=092/A=001588
20260208171638OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=078/A=001588
20260208174654OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=100/A=001588
20260208181709OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=096/A=001588
20260208184721OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=100/A=001588
20260208191736OE3OEK-11>APRSGW,TCPIP*,qAR,OE3OEK-11:!4740.51N/01556.92E-/B=100/A=001588