APRS Packet Errors for JH5QYZ-12 (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
20260209092902JH5QYZ-12>APERXS,WIDE1-1,qAR,JA5HWI-10:!3349.55N/13350.47E>275/031/A=000000
20260209093042JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3349.33N/13242.76E>242/020/A=000000
20260209093308JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3349.69N/13242.66E>282/013/A=000019
20260209093417JH5QYZ-12>APERXS,WIDE1-1,qAS,JA5XQF-10:!3349.70N/13242.50E>007/007/A=000009
20260209093735JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3350.46N/13242.52E>320/023/A=000013
20260209093943JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3351.08N/13242.78E>191/010/A=000099
20260209100220JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3349.85N/13242.52E>198/025/A=000000
20260209100311JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3349.68N/13242.51E>146/008/A=000000
20260209100318JH5QYZ-12>APERXS,WIDE1-1,qAS,JA5XQF-10:!3349.67N/13242.54E>099/014/A=000000
20260209100530JH5QYZ-12>APERXS,WIDE1-1,qAR,JA5HWI-10:!3349.63N/13242.79E>183/019/A=000000
20260209100726JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3349.25N/13242.81E>187/019/A=000004
20260209100834JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3348.97N/13242.58E>301/005/A=000000
20260209100956JH5QYZ-12>APERXS,WIDE1-1,qAR,JH5HOA-10:!3348.93N/13242.36E>013/004/A=000049