Burndy KVS26 has 6 recorded cross-reference matches across 6 manufacturers. Compare the listed alternatives and check their source notes before selecting a replacement.
Two-way recorded relationships. Each source may carry conditions or differences.
Blackburn 2B20BB versus Burndy KVS26:
Type 2B – Two-bolt connectors without spacer. Confirm conductor material and size, conductor count, mounting geometry, torque requirements and applicable ratings before substitution.
Penn Union VT-1 versus Burndy KVS26:
Type 2B – Two-bolt connectors without spacer. Confirm conductor material and size, conductor count, mounting geometry, torque requirements and applicable ratings before substitution.
Burndy KVS26 versus Anderson K-2:
Type 2B – Two-bolt connectors without spacer. Confirm conductor material and size, conductor count, mounting geometry, torque requirements and applicable ratings before substitution.
Burndy KVS26 versus Dossert DSU13:
Type 2B – Two-bolt connectors without spacer. Confirm conductor material and size, conductor count, mounting geometry, torque requirements and applicable ratings before substitution.
Burndy KVS26 versus Chance OOUC:
Type 2B – Two-bolt connectors without spacer. Confirm conductor material and size, conductor count, mounting geometry, torque requirements and applicable ratings before substitution.
Burndy KVS26 versus Kearney 16369:
Type 2B – Two-bolt connectors without spacer. Confirm conductor material and size, conductor count, mounting geometry, torque requirements and applicable ratings before substitution.
No part-specific datasheet link has been verified in this record. Catalog and document-search links are provided to help locate current specifications.
Counts describe recorded relationships, not stock, sales, testing or independent qualification. Manufacturer-and-part identities remain separate. Indexing dates do not establish current specifications or availability.
Check current manufacturer documents and electrical, mechanical, environmental and application requirements before selecting a replacement.
How ExactCross handles cross-reference data →