Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-hide-security-enhancer domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/luda3944/fooot/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-wp-security domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/luda3944/fooot/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the instagram-feed domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/luda3944/fooot/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the woocommerce domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/luda3944/fooot/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/luda3944/fooot/wp-includes/functions.php on line 6114
VL1 : Lupopo et V. Club s’affrontent sur le terrain administratif - NDEMBO.NET
FeaturedFootball nationalLinafoot

VL1 : Lupopo et V. Club s’affrontent sur le terrain administratif

Le leader du championnat national et son dauphin sont au cœur d’une bataille administrative. Lupopo accuse V. Club d’avoir aligné un joueur litigieux lors du choc entre les deux clubs le 15 décembre 2022. Les Viets estiment que Taddy Etekiama n’était pas éligible pour cette rencontre. Côté V. Club, la contre-offensive est proportionnelle à l’attaque. Le club kinois conteste l’éligibilité de Jean-Marc Makusu.

En attendant de trancher ce double litige, la LINAFOOT, organisatrice du championnat national, a suspendu le résultat de la rencontre. Conséquence: V. Club, avec 3 points de moins, en compte désormais 28 en 10 sorties, soit 6 de plus que son dauphin lushois qui a livré 9 rencontres.

MNK

Articles similaires

Bouton retour en haut de la page