APRS Packet Errors for OK1NP-7 (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
20250111140858	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB,qAS,DB0FGB:!4943צר‚/נ=322.46E>/A=001113LoRa Tracker !wGH!
20250111141358	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB*,qAS,DB0FGB:!4943.6_,!1322.46E>/A=001092LoRa Tracker !wzc!
20250111142858	OK1NP-7>APLT00-1,OK1CMJ-14*,qAR,OK1KUN-2:!4943.69N/013ע2.45E>/A=001179LoRa Tracker !wEk!
20250111143358	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB*,qAS,DB0FGB:!4943.V9>)S4322.46E>/A=001162LoRa Tracker !w@A!
20250111151858	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB*,qAS,DB0FGB:!4943.&)N/ 13RT.45E>/A=001151LoRa Tracker !w)P!
20250111153858	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB*,qAS,DB0FGB:!4943.6)N/11322.45E>/A=001188LoRa Tracker !w(h!
20250111160858	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB*,qAS,DB0FGB:!4943.68N/01?ע2ג46E>/A=001132LoRa Tracker !wOD!
20250111165358	OK1NP-7>APLT00-1,OK1CMJ-14,DB0FGB*,qAS,DB0FGB:!4943.68N/0a327~45E>/A=001107LoRa Tracker !wsX!