redux-framework 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/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131acf 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/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131woocommerce 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/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap 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/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131customized-task-offer 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/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131workreap-hourly-addon 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/runcloud/webapps/uplancer/wp-includes/functions.php on line 6131| Management number | 214487397 | Release Date | 2026/04/12 | List Price | $16.22 | Model Number | 214487397 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
Elevate your equestrian wardrobe with the Dublin Everyday Bling Riding Gloves II. These gloves don't just enhance your grip and control; they add a touch of glamour to your ride with their sparkling rhinestone detailing. Built for all-day comfort, they are crafted from stretchable synthetic KT-Serino material, offering a breathable yet snug fit that moves perfectly with your hands. Whether you're on a casual hack or gearing up for a competition, these gloves deliver unmatched functionality with a splash of elegance. And with their touch screen compatibility, you’ll never miss a moment to capture the perfect riding snapshot or check your riding apps without removing them. Designed with an adjustable touch tape wrist closure, they promise a custom, secure fit, ensuring you stay focused on the ride ahead. Practicality, comfort, and style; these gloves have it all.
| Size | M/7 |
|---|---|
| Brand | Dublin |
| Color | Navy |
| Sport | Equestrian |
| Pattern | Solid |
| Material | Nylon, Polyurethane |
| Brand Name | Dublin |
| Model Name | Everyday Bling Riding Gloves |
| Item Weight | 8 ounces |
| Part Number | 1022306008 |
| Closure Type | Hook and Loop |
| Manufacturer | Weatherbeeta USA Inc. |
| Package Weight | 0.5 Pounds |
| Number of Items | 1 |
| Special Feature | Flexible, Lightweight, Slip Resistant, Touch Screen Support, Windproof |
| Suggested Users | unisex-adult |
| Hand Orientation | Ambidextrous |
| Included Components | GLOVES |
| Warranty Description | Standard Manufacturer's Warranty |
| Age Range Description | Adult |
| Item Package Dimensions L x W x H | 12 x 4.5 x 1.5 inches |
| Global Trade Identification Number | 09355776197104 |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form