APRS Packet Errors for N2XP-2 (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
20260909000921	N2XP-2>APTW14,TOMRVR,WIDE1*,WIDE2-1,qAR,W2SRH:_09081737c165s00g000t077r000p000P000h67b10246tU2k
20260909095005	N2XP-2>APTW14,TOMRVR,WIDE1,W2ZQ,WIDE2*,qAR,W2SRH:_09090317c208s00g000t069r000p000P000h93b10245tU2k
20260909181417	N2XP-2>APTW14,TOMRVR,WIDE1*,WIDE2-1,qAR,W2SRH:!395892N/07408.84W_wxTrak n2xp@arrl.net