APRS Packet Errors for KR4BHH-9 (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
20260209131742KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3713.18N/07917.42Wk051/047/A=000610MONITORS WA1ZMS
20260209131944KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3714.15N/07916.84Wk340/042/A=000702MONITORS WA1ZMS
20260209132348KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3716.62N/07915.13Wk014/046/A=000793MONITORS WA1ZMS
20260209132550KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3717.66N/07913.97Wk014/046/A=000797MONITORS WA1ZMS
20260209132752KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3718.74N/07914.28Wk348/012/A=000826MONITORS WA1ZMS
20260209132954KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,KN4EFJ-7:!3719.32N/07913.95Wk046/000/A=000859MONITORS WA1ZMS
20260209133156KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3719.74N/07914.75Wk292/026/A=000846MONITORS WA1ZMS
20260209133358KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,KN4EFJ-7:!3720.35N/07914.29Wk032/043/A=000800MONITORS WA1ZMS
20260209134010KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3721.73N/07914.70Wk266/000/A=000666MONITORS WA1ZMS
20260209134416KR4BHH-9>APAT51,N4IW-10*,WIDE2-1,qAR,N4VGW-1:!3721.87N/07914.92Wk239/000/A=000708MONITORS WA1ZMS
20260209134616KR4BHH-9>APAT51,WIDE1-1,WIDE2-1,qAR,N4VGW-1:!3721.87N/07914.92Wk239/000/A=000708MONITORS WA1ZMS