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 | 209984842 | Release Date | 2026/04/02 | List Price | $104.66 | Model Number | 209984842 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
VERSATILE DRILLING TOOL: This Trend Snappy 9.5mm countersink comes with a 2.5mm HSS drill for precise countersinks and counterbores in hard and softwoods. For use with Imperial No6 gauge screws in softwood and metric screws up to 5mm gauge in other materials.ADJUSTABLE PILOT DRILL: Features an easily adjustable pilot drill length for different timber thicknesses and fast alignment. Ensures clean, consistent finishes every time.QUICK RELEASE COMPATIBLE: Designed with a quick release system for seamless integration with your existing setup. Suitable for use with Trend Snappy SNAP/PC/95T or SNAP/PC/38 Plug Cutters when fixings need to be hidden.DURABLE CONSTRUCTION: Made from hardened tool steel, this countersink guarantees long-lasting performance and durability. It's equipped with a high-quality, replaceable 2.5mm HSS (High Speed Steel) drill for added convenience and longevity.1/4 INCH HEX SHANK: With a 1/4 inch hex shank diameter, this countersink drill bit is designed for easy and quick bit changes, enhancing your efficiency during woodworking tasks.
| Model | SNAP/CS/6 |
|---|---|
| Brand Name | TREND |
| Shank Type | Hex |
| Unit Count | 1.0 Count |
| Item Weight | 1.12 ounces |
| Finish Types | Hss |
| Manufacturer | Trend |
| Material Type | High Speed Steel (HSS) |
| Item Type Name | No.6 9.5mm(3/8") Diameter Countersink With Adjustable 3/32in Pilot Drill For No6 Screws |
| Item Dimensions | 5.91 x 3.15 x 0.55 inches |
| Tool Flute Type | Spiral |
| Cutting Diameter | 9.5 Millimeters |
| Number of Flutes | 2 |
| Included Components | 1 x Snappy Countersink with 3/32 (2.5mm) Drill |
| Cutting Angle String | 6E+1 Degrees |
| Surface Recommendation | Wood |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form