APRS Packet Errors for HS1AH-10 (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
20251214215505HS1AH-10>AESPG4,qAR,HS1AL-1:=1453.85ꊂr*HS1AH 145.700 PM 1:[14] , 2.5:[18] , 10:[25] (μgkJ
20251215114706HS1AH-10>AESPG4,qAR,HS1AL-1:=145 r10023.8Q$j!145.700 PM 1:[9] , 2.5:[13] ,[14] (μg/m3)
20251215121820HS1AH-10>AESPG4,qAR,HS1AL-1:=1453r10023.88E#HS1AH 145.700 PML, 2.5:, 10:[14] (μg/m3)
20251215134806HS1AH-10>AESPG4,qAR,HS1AL-1:=1453.8M)r*HS1A5.700 PM8] , 2M+&Sb7] (μg/m3)
20251215135837HS1AH-10>AESPG4,qAR,HS1AL-1:=1453 r10023.8Q$j!145 PM 1:[1MW 2.5:[22] , 10:[24] (μg/[
20251215154949HS1AH-10>AESPG4,qAR,HS1AL-1:=1453r10023.88E#HS1AH 145.700 PML, 2.5:[16] , 10:[16] (μg/m3)
20251215160030HS1AH-10>AESPG4,qAR,HS1AL-1:=1453.85N/1002 HS1AH 145.700 PM 1:[12] ,&7] , 1(μgkJ
20251215161044HS1AH-10>AEi94,qAR,HS1AL-1:=1453r10023.88E#HS1AH 145.700 PML, 2.5:[18] , 10:[20] (֩kJ
20251215163129HS1AH-10>AESPG4,qAR,HS1AL-1:=1453.85N/r*HS1A5.700 PM3] , 2M+&b5] (μg/m3)
20251215185446HS1AH-10>AESPG4,qAR,HS1AL-1:=1453.85N?L.88E#HSLP5.700 PS2] , 2.M, 10:[16] (μg/m3)
20251215201124HS1AH-10>AESPG4,qAR,HS1AL-1:=1453.85N/10& E#HS1AHLS邂PM 1:[15] , 2.5:[21] , 10:[2MWBrg/m3)