APRS Packet Errors for OH2DPN (last 24 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
20261024045445OH2DPN>APZNEO,OH2RDK-7,WIDE1*,WIDE2-2,qAR,OH7JHF-1:=6011.79N/02507.4E-PHG2330NeoAPRS
20261024065023OH2DPN>APZNEO,WIDE1*,WIDE2-2,qAR,OH2RCH-1:)TBN_6011.79N/02507.40ErTBN Test Item
20261024065523OH2DPN>APZNEO,WIDE1*,WIDE2-2,qAR,OH7JHF-1:)TBN_6011.87N/02510.46ErTBN Test Item
20261024065824OH2DPN>APZNEO,WIDE1*,WIDE2-2,qAR,OH2RCH-1:)TBN_6011.87N/02510.46ErTBN Test Item
20261024105732OH2DPN>APZNEO,WIDE1*,WIDE2-2,qAR,OH7JHF-1:;TBN *241057z6011N/02510.50ErTBN Tx Stn
20261024111032OH2DPN>APZNEO,OH2RDK-7,WIDE1*,WIDE2-2,qAR,OH7JHF-1:;TBN *24111z6011.87N/02550Er360/000TBN Tx Stn
20261024112235OH2DPN>APZNEO,WIDE1*,WIDE2-2,qAR,OH7JHF-1:;TBN *241122z6011.87N/02510.50Er360/000TBN Tx Stn