APRS Packet Errors for KE0JZE (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
20250509093333KE0JZE>APN000,K0ATT-10,WIDE1*,WIDE2-1,qAR,WB0HTW:=3833.84N/0¹118.36W#VR-N7500 DIGI/iGAT 22.50V
20250509093636KE0JZE>APN000,K0ATT-10,WIDE1*,WIDE2-1,qAR,WB0HTW:=3;35.84N/09018.36W#VRMN7500 DIGI/iGAT 12.47V
20250509094441KE0JZE>APN000,K0ATT-10,WIDE1*,WIDE2-1,qAR,WB0HTW:=3833î84N/09014.36W#VR-N7500 DIGI/jGA” 12.45V
20250509095445KE0JZE>APN000,K0ATT-10,WIDE1-8*,WIDEr-1,qAR,WB0HTW:=3833-84N,09018.36W;VR-N7500 DIGI/iGAT 12.44V
20250509095842KE0JZE>APN000,K0ATT-10,WIDE1*,WIDu2-1,qAR,WB0HTW:=383384N/09018.36W#VR-N7500 DIGI/iGAT 12.47V
20250509102513KE0JZE>APN000,K0ATT-10,WIDE18*,WIDE2-1,qAR,WB0HTW:=3833.84N/090=8.36W#VR-N7500 DIGJ/iGAT 12.45V
20250509103404KE0JZE>APN000,K0ATT-10,WIDE1*,WIDE2-1,qAR,WB0HTW:=3833.8N/39018.36W#VR-N7500 D)GI/iGAT 12.43V
20250509104010KE0JZE>APN000,K0ATT-10,WIDE1*,WIDE2-1,qAR,WB0HTW:=3833.84N/°8018.36W#VR-N7500 DOG)/iGAT 12.47V