APRS Packet Errors for LD3TB (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
20260209103041LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209110107LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209113153LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209120218LD3TB>APOT21,WIDE2-1,qAR,LD3HV:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209123246LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209130326LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209133351LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209140407LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209143426LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209150502LD3TB>APOT21,WIDE2-1,qAR,LD3HV:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209153554LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg
20260209160620LD3TB>APOT21,WIDE2-1,qAR,LD1FE:!5916.98NS01024.36E#PHG2260 W3, NORn Toensberg