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 /var/www/html/staging/wp-includes/functions.php on line 6114mailpoet 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 /var/www/html/staging/wp-includes/functions.php on line 6114ninja-forms 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 /var/www/html/staging/wp-includes/functions.php on line 6114woocommerce-more-sorting 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 /var/www/html/staging/wp-includes/functions.php on line 6114flexible-shipping 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 /var/www/html/staging/wp-includes/functions.php on line 6114woocommerce-payments 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 /var/www/html/staging/wp-includes/functions.php on line 6114instagram-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 /var/www/html/staging/wp-includes/functions.php on line 6114rocket 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 /var/www/html/staging/wp-includes/functions.php on line 6114wpforms-lite 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 /var/www/html/staging/wp-includes/functions.php on line 6114goya 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 /var/www/html/staging/wp-includes/functions.php on line 6114translatepress-multilingual 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 /var/www/html/staging/wp-includes/functions.php on line 6114mailchimp-for-wp 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 /var/www/html/staging/wp-includes/functions.php on line 6114Pour compléter votre bas de soupière, en recomposer une dépareillée ou faire une déco murale
Diamètre 26 cm
En excellent état
]]>Diamètre 22 cm Hauteur 4 cm
En parfait état
Vaisselle ancienne fin XIX°
]]>
26 cm
Décor hivernal en camaïeu de verts
Légère patine mais bel état général sans accidents
Vaisselle ancienne fin XIX° début XX°
]]>Vaisselle ancienne à décor en camaïeu de verts
23,5 cm X 11,5 cm
Légère patine sur l’un mais pas d’accidents
Vendus en lot de deux
]]>Décor en camaïeu de vert
En parfait état
Vendues à l’unité
Vaisselle ancienne, fin XIX° début XX°
]]>Décor en camaïeu de vert
Légère patine, pas de fêles ou éclats
Vendues à l’unité
Vaisselle ancienne, fin XIX° début XX°
]]>Suite à la guerre de Bismarck (1871) qui annexe l’Alsace et la Lorraine à l’Allemagne, Paul de Geiger, alors directeur de la faïencerie de Sarreguemines, décide en 1876 de la construction d’une usine sur le territoire français, pour pallier l’augmentation du prix de ses produits (taxés à 15%) en France. La construction à Digoin (Saône et Loire) de cette nouvelle unité de production débutera en 1877. C’est pourquoi certaines productions anciennes de Sarreguemines portent l’estampille « Sarreguemines Digoin ». Cette production, estampillée U&Cie Sarreguemines, semble donc bien antérieure.
]]>Suite à la guerre de Bismarck (1871) qui annexe l’Alsace et la Lorraine à l’Allemagne, Paul de Geiger, alors directeur de la faïencerie de Sarreguemines, décide en 1876 de la construction d’une usine sur le territoire français, pour pallier l’augmentation du prix de ses produits (taxés à 15%) en France. La construction à Digoin (Saône et Loire) de cette nouvelle unité de production débutera en 1877. C’est pourquoi certaines productions anciennes de Sarreguemines portent l’estampille « Sarreguemines Digoin ». Cette production, estampillée U&Cie Sarreguemines, semble donc bien antérieure.
]]>