RSA-3010-C
RF Industries ↗RF Industries RSA-3010-C has 14 recorded cross-reference matches across 8 manufacturers. Compare the listed alternatives and check their source notes before selecting a replacement.
RSA-3010-C equivalent products & cross references
Two-way recorded relationships. Each source may carry conditions or differences.
901-9531-2
901-9873
RF Industries RSA-3010-C versus Amphenol 901-9873:
RFI connector has nickel plating, this connector has gold.
901-9880-RFX
39P121-12
RF Industries RSA-3010-C versus Berg 39P121-12:
RFI connector is nickel plated brass, this connector is Passivated Stainless-Steel.
28-5024
142-0407-101
RF Industries RSA-3010-C versus Johnson 142-0407-101:
RFI connector has nickel plating, this connector has gold.
142-0407-106
2037-5005-02
RF Industries RSA-3010-C versus MA/COM 2037-5005-02:
RFI connector is nickel plated brass, this connector is Passivated Stainless-Steel.
2037-5056-02
RF Industries RSA-3010-C versus MA/COM 2037-5056-02:
RFI connector is nickel plated brass; this connector is stainless steel with passivated coupling nut. RFI connector has non-captive contact.
2837-7358-02
RF Industries RSA-3010-C versus MA/COM 2837-7358-02:
RFI connector is nickel plated brass; this connector is stainless steel with passivated coupling nut. RFI connector has non-captive contact.
PE4405
R125175
RF Industries RSA-3010-C versus Radiall R125175:
RFI connector has nickel plating, this connector has gold.
19-02F-2-TGN
RF Industries RSA-3010-C specifications & datasheets
No part-specific datasheet link has been verified in this record. Catalog and document-search links are provided to help locate current specifications.
Source coverage & limitations
- User provided
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 →