APRS Packet Errors for HS3LSE-10 (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
20240416052221HS3LSE-10>APINDY,WIDE1-1,APRS,qAR,E24KHS-3:)SRNEMT02!1452.65N/10330.™*…Å68/001/A=000498 SAT:08 StandBy
20240416052651HS3LSE-10>APINDY,WIDE1-1,APRS,qAR,E24KHS-3:)SR-NADEE!1452.57N/1033L)²*…Å84/002/A=000488 SAT:9 NADEE
20240416054626HS3LSE-10>APINDY,WIDE1-1,APRS,qAR,HS3LSE-5:)SRNEMT02!1452.10N/1032œI‚*…Á35/001/A=000492 SAT:09 StandBy
20240416085235HS3LSE-10>APINDY,WIDE1-1,WIDE2-1,qAR,HS3LSE-1:)SRNVR01!LS“i‚r½10330.30Ea214/046
20240416085315HS3LSE-10>APINDY,WIDE1-1,APRS,qAR,HS3LSE-5:)SRNEMT02!1451.67N/LššŠršÂ*…Í03/000/A=000472 SAT:10 StandBy
20240416085328HS3LSE-10>APINDY,WIDE1-1,WIDE2-1,qAR,E24KHS-3:)SRNVR01!1453.84N/10330KŠ*…Å69/006
20240416085657HS3LSE-10>APINDY,WIDE1-1,APRS,qAR,HS3LSE-1:)SRNEMT02!14M&‰‚r½10330.37Ea305/001/A=000462 SAT:11 StandBy
20240416091933HS3LSE-10>APINDY,WIDE1-1,APRS,qAR,HS3LSE-5:)SRNEMT02!1453.33N/10329—“*…Å17/000/A=000518 SAT:11 StandBy