APRS Packet Errors for LA4FSA-7 (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
20250721171739LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@171737h6553.620/E2[725/125La4fsa Rune
20250721171942LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@171940h6553204N/01315.64E[120/000La4fsa Rune
20250721172146LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@172143h6553.610/E0[725/128La4fsa Rune
20250721173809LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@173807h6553.620/E0[725/116La4fsa Rune
20250721175506LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@175504h653.621N/01315.63E[299/000La4fsa Rune
20250721183642LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@183640h6556226N/01315.64E[024/000La4fsa Rune
20250721184251LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@184249h653.621N/01315.64E[124/000La4fsa Rune
20250721184657LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@14655.h6553.62N/0135.644E[124/000La4fsa Rune
20250721185712LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@85710.h6553.62N/0315.651E[124/001La4fsa Rune
20250721190746LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@19744.h6553.62N/01315461E[124/000La4fsa Rune
20250721194957LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@194955h53.6194N/01315.65E[175/000La4fsa Rune
20250721204247LA4FSA-7>APBM1D,LD8MV,DMR*,qAR,LD8MV:@204245h653.621N/01315.65E[082/000La4fsa Rune