APRS Packet Errors for N7UW-1 (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
20260927220958N7UW-1>APMI06,WIDE2-2,qAS,AE7AF:@272012z4183N558.#WX3in1Plus2.0, Jelm Mt. WY
20260927222000N7UW-1>APMI06,WIDE2-2,qAR,MAGMTN:;147.01522022z4105.82N/10558WrT146 Jelm Mt., U N7UW
20260927233459N7UW-1>M0,TN,qAR,AE7AF:;05 *137zN/105589WrT146.2, Jelm Mt., UARC N7UW
20260927235506N7UW-1>6WIDETN,qAR,AE7AF:;0 *z4111053T146iverf Wy UAR
20260928012500N7UW-1>APMI06,WIDEGMTN,qAR,AE7AF:;5 *27105.828.59Wr146.2, Jelm MRC N7U
20260928015500N7UW-1>APMI06,WIDE2-2,qAR,MAGMTN:;147.015 *274105.82N/10558.59Wr, Jelm Mt., UARC N
20260928024523N7UW-1>APMI06,N*,WIDE2-1,qAS,AE7AF:;1 *28004782N/10558. Jelm Mt., UARC N7UW
20260928024954N7UW-1>APMI06E-2,qAS,AE7AF:@284105.8558.60in1Plu Jelm
20260928025001N7UW-1>APM2-1,qAS,AE7AF:;14280052z4105.N10558.546.2 Mt., 7W
20260928030459N7UW-1>APM6,WIDEAR,MAG,qAR,AE7AF:;147.107z4182N/10.9WrT146.Jelm Mt., UARC N7UW
20260928033007N7UW-1>APMI06,WIDE2-2N,qAR,AE7AF:;146.610 *280132z4118.89NT146.2, of Wyoming,