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 | 211167728 | Release Date | 2026/04/04 | List Price | $36.00 | Model Number | 211167728 | ||
|---|---|---|---|---|---|---|---|---|---|
| Category | |||||||||
PST Scope Sterilization Tray safeguards delicate scopes during sterilization. Its unique grid system simplifies installation of mats or silicone bars for instrument protection. Integral feet on the base and corner ridges on the lid facilitate handling in autoclaves and storage. The see-through lid enables easy inspection while providing protection during transport. All trays are crafted from GE's ULTEM resin, ensuring strength, structural integrity, and longevity, and endure standard sterilization methods like steam autoclave, dry heat, or chemical. Available in three configurations with varying sizes: Base and Lid Only, Base and Lid with protective Mat, or Base and Lid with removable Silicone Bars for secure scope placement (bars accommodate scopes from 1 mm to 10 mm in diameter).
| Color | White |
|---|---|
| Shape | Rectangular |
| Theme | Medical |
| Occasion | professional use |
| Tray Type | Medical Scope Sterilization Tray |
| Brand Name | Plastic Sterilization Tray Corp |
| Finish Types | Smooth |
| Manufacturer | PST |
| Material Type | Plastic |
| Special Feature | Available in three configurations: Base & Lid Only, Base & Lid with protective Mat, or Base & Lid with removable Silicone Bars, Lightweight yet extremely durable plastic trays for sterilizing delicate scopes, See-through lid provides easy identification, Sterilizable by all standard methods, Unique grid system makes it easy to install mats or silicone bars for instrument protection |
| Manufacturer Part Number | 2970011505 |
| Product Care Instructions | Clean and sterilize according to standard medical equipment procedures. |
| Recommended Uses For Product | Sterilizing delicate scopes |
If you notice any omissions or errors in the product information on this page, please use the correction request form below.
Correction Request Form