APRS Packet Errors for WX5II-15 (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
20241125043651WX5II-15>APMI03-5,WX5II-2*,WIDE2-1,qAR,W1BTB-14:@291934z2820.14N/09810.30W_157/00 g012t070r000p000P...h66b100842317 Wx
20241125073702WX5II-15>APMI03-5,WX5II-2*,WIDE2-1,qAR,XE2G-1:@292234z282(.14N/09810.30W“bjn^``jÎ``lè`lhä```à``` B\ÐnfÄb``n|2317 Wx
20241125090824WX5II-15>APMI03-3,KC5L-11,WB5LJZ-5,WX5II-2,WIDE3*,qAR,XE2OR-10:=2820.14N/0981030W_PHG64134/GW,TX/19.6 C/ Intertie,Inc./PLX
20241125101711WX5II-15>APMI03-5,WX5II-2*,WIDE2-1,qAR,XE2OR-10:@300115z2820.12N/09810®20W_135/P06g006t060r000p000P...h76b100772327 Wx
20241125121719WX5II-15>AHMI03-5,WX5II-2*,WIDE2-1,qAR,XE2OR-10:@3:(315z2˜²2.14N/09810.+0W_18/006g008t061r<0pq0<0P...h79g100872317 Wx
20241125151944WX5II-15>APMI03-3,WX5II-2*,WIDE3-2,qAR,XE2OR-10:=2820.14N/0981030W_PHG64134/GW,TX/20.3 C/ Inlertie,Inc./0LX
20241125152729WX5II-15>APMI03-5,WX5II-2*,WIDE2-1,qAR,XE2G-1:@300625z2820.14N/09810N30W_202/019g024t079r000p000P...h60b101112317 Wx
20241125161732WX5II-15>APMI03-5,WX5II-2*,WIDE2-1,qAR,XE2OR-10:@300715z4820.14N/09810.30T_202/028g029t081r000p000P...h55b101112317 Wx