APRS Packet Errors for DJ2FR (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
20251224161920DJ2FR>APLRT1,WIDE1-1,qAO,DG2SER-10:!/6&I`Q?eK_ lQ.../...g...t062r...p...P...h34b10219
20251224162924DJ2FR>APLRT1,WIDE1-1,qAO,DG2SER-10:!/6&J/Q?eH_ eQ.../...g...t062r...p...P...h33b10209
20251224163928DJ2FR>APLRT1,WIDE1-1,qAO,DG2SER-10:!/6&IYQ?eO_ rQ.../...g...t061r...p...P...h33b10226
20251224164932DJ2FR>APLRT1,WIDE1-1,qAO,DL4MHA-10:!/6&IQ?eO_ vQ.../...g...t059r...p...P...h34b10231
20251224165936DJ2FR>APLRT1,WIDE1-1,qAR,DL8MFF-10:!/6&IiQ?eO_ kQ.../...g...t056r...p...P...h36b10218
20251224170940DJ2FR>APLRT1,WIDE1-1,qAO,DG2SER-10:!/6&J"Q?e[_ {Q.../...g...t054r...p...P...h38b10237
20251224171944DJ2FR>APLRT1,WIDE1-1,qAO,DG2SER-10:!/6&I{Q?eb_ yQ.../...g...t051r...p...P...h40b10235