APRS Packet Errors for F6KBR-2 (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
20250516062103	F6KBR-2>APFD66,F1ZNT-3,WIDE2-2,qAO,F1UFD:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516062205	F6KBR-2>APFD66,F6KBR-4,F5ZWN-3,WIDE2-1,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516065018	F6KBR-2>APFD66,F1ZCJ-3,WIDE2-2,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516074848	F6KBR-2>APFD66,F1ZCJ-3,WIDE2-2,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516081802	F6KBR-2>APFD66,F1ZCJ-3,WIDE2-2,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516094550	F6KBR-2>APFD66,F1ZCJ-3,WIDE2-2,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516101505	F6KBR-2>APFD66,F1ZCJ-3,WIDE2-2,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516104423	F6KBR-2>APFD66,F6KBR-4,F5ZWN-3,WIDE2-1,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516111335	F6KBR-2>APFD66,F1ZCJ-3,WIDE2-2,qAR,F1GRH-10:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m
20250516114254	F6KBR-2>APFD66,F1ZJM-3,WIDE2-2,qAO,F1UFD:!42#5.94NV00221.79E#PHG3842 Digi APRS66 Foret de CON@T * 990m