# 25 Pair Color Code: Tip, Ring and Binder Records **Meta description:** 25 pair color code guide: tip and ring colors, binder groups, RUS cable counts, splice records and pair assignments for copper maintenance and fiber migration. **Primary keyword:** 25 pair color code **Published:** November 6, 2026 **Last updated:** November 6, 2026 By Omar Molina | October 19, 2026 | 11 min read ![A worker in a safety vest sorts colored twisted wire pairs from a black cable beside an open green cabinet.](/blog/img_25_pair_color_code.webp) IN THIS ARTICLE - [How the 25 pair color code works](#sequence) - [Read the 25 pair color code chart](#chart) - [Binder groups carry the count beyond 25 pairs](#binders) - [Turn physical colors into usable assignment records](#records) - [Use copper records through splicing and fiber migration](#migration) - [Choose the next step for your copper records](#next) A readable pair color can still lead to the wrong circuit. The same white/blue combination repeats inside every standard binder group, and the cable serving a terminal may carry a different assignment range from the cable entering its upstream splice. We use the color sequence to establish physical identity, then reconcile that identity with the owner's records. This guide covers the complete pair sequence, larger cable counts and the documentation decisions that matter when copper remains in service during a fiber build. ## How the 25 pair color code works The 25 pair color code identifies 25 twisted telephone pairs using five primary colors and five secondary colors. Primary colors identify tip conductors; secondary colors identify ring conductors. Each primary color combines with all five secondary colors, producing a repeatable sequence that supports pair identification within a cable binder group. ### Primary and secondary colors The primary, or major, sequence is **white, red, black, yellow and violet**. The secondary, or minor, sequence is **blue, orange, green, brown and slate**. Slate means gray in this convention. Keep the order fixed. We read the secondary sequence completely before advancing to the next primary color, so white/slate is followed by red/blue rather than another white pair. That rule produces pair 1 as white/blue and pair 25 as violet/slate. There are 50 insulated conductors in those 25 pairs. We retain the word pair in drawings because a conductor count and a pair count describe different quantities, even when both appear beside the same cable symbol on a plan. The reference for the sequence here is the Rural Utilities Service's *RUS standard for splicing copper and fiber optic cables*, 7 CFR 1755.200(c)(5), Tables 1 through 3, reproduced in the CFR edition revised as of January 1, 2025. Table 1 assigns individual pair colors. Tables 2 and 3 establish binder and super-unit identification. These are technical reference conventions; the applicable owner specification governs the particular plant. ### Tip, ring and tracer marks Tip and ring name the conductors within a telephone pair. Where insulation carries reciprocal tracer colors, the tip conductor has the primary base color with the secondary tracer, and the ring conductor has the secondary base color with the primary tracer. For pair 1, that means white with blue identification and blue with white identification. Read both conductors together. Tracer presentation depends on cable construction. We do not require every existing cable to look like a newly printed chart before accepting its identity. Instead, we compare the insulation system with its cable specification and verify continuity under the owner's procedure when markings are unclear or the records disagree with the exposed cable. A color assignment does not prove operating polarity. Nor does it establish whether a circuit is active, electrically sound or safe to disturb. Our drawings retain tip and ring identity through each connection, but field personnel must use the applicable testing and work controls before disconnecting any conductor. Color alone cannot authorize a cut. ## Read the 25 pair color code chart Use the primary color to select a row, then read across the secondary sequence shown in that row. The grouped chart below covers every pair from 1 through 25 without requiring a separate table for each conductor. Both conductors belong to the same twisted pair; the slash separates tip and ring color designations. For an arithmetic check, assign primary positions 1 through 5 and secondary positions 1 through 5 in their stated order. The pair number equals five times the primary position minus five, added to the secondary position. Black is primary position 3 and green is secondary position 3, so black/green identifies pair 13. We use that calculation as a cross-check when transcribing a splice sheet. It catches an index error. It cannot correct a conductor that has been separated from its mate, and it cannot establish which binder surrounds the pair when the binding has already been removed. | Pair range | Tip color | Pair number and ring color | End-of-row check | | --- | --- | --- | --- | | 1 to 5 | White | 1 blue; 2 orange; 3 green; 4 brown; 5 slate | 5 = white/slate | | 6 to 10 | Red | 6 blue; 7 orange; 8 green; 9 brown; 10 slate | 10 = red/slate | | 11 to 15 | Black | 11 blue; 12 orange; 13 green; 14 brown; 15 slate | 15 = black/slate | | 16 to 20 | Yellow | 16 blue; 17 orange; 18 green; 19 brown; 20 slate | 20 = yellow/slate | | 21 to 25 | Violet | 21 blue; 22 orange; 23 green; 24 brown; 25 slate | 25 = violet/slate | The table follows RUS Table 1. For example, red/brown is pair 9, while yellow/orange is pair 17. Reversing the words should not reverse the pair assignment in a database: we specify which field means tip and which means ring, rather than letting a slash-delimited label carry an unstated convention. **Preserve the mate:** When documenting exposed conductors, record the twisted pair before separating it for a photograph or termination detail. Two individually readable colors can lose their meaning if the original pair relationship disappears. ## Binder groups carry the count beyond 25 pairs A 100-pair cable contains four standard 25-pair groups. Each group repeats the same conductor sequence, while its binder identifies the group's position in the cable. The binder colors therefore belong in a separate record field. We never treat a white/blue binder as proof that every conductor inside it belongs to pair 1. ### Group identity and cable pair number RUS Table 2 assigns white/blue to cable pairs 1 through 25, white/orange to 26 through 50, white/green to 51 through 75 and white/brown to 76 through 100. The next binder is white/slate, carrying 101 through 125. Red/blue follows it with 126 through 150. The pair sequence inside each group starts over. Consider cable pair 38 as a worked example, not a project record. It belongs to the white/orange binder because that group contains pairs 26 through 50. Subtract 25 to obtain local pair 13, which is black/green. A complete physical identification therefore includes the cable identity, white/orange binder and black/green pair. Leaving out the binder makes the identification ambiguous. We write the cable pair number separately from the pair's position within its binder. For consecutive full groups, cable pair number equals 25 times the number of preceding groups, added to the local pair number. Check the cable construction first. Partial groups and separately identified service pairs require the applicable cable schedule rather than an assumed count. ### The 600-pair boundary RUS Table 2 stops at binder group 24, violet/brown, covering pairs 576 through 600 within a super-unit. It does not add a violet/slate group to make 625 pairs. That distinction matters. We preserve the hierarchy in records instead of extending the familiar 25-pair sequence past the boundary stated by the specification. Table 3 gives the next level: white identifies super-unit pairs 1 through 600, red identifies 601 through 1200, black identifies 1201 through 1800, yellow identifies 1801 through 2400 and violet identifies 2401 through 3000. The table continues with secondary colors for still larger counts. Confirm that hierarchy against the installed cable's construction before applying it. For example, pair 638 lies in the red super-unit, within its white/orange binder, at local pair 13. The conductors remain black/green. We recommend storing those levels independently so a label change can be checked without losing the relationship between the physical cable and its numbered pair inventory. A real limitation of this hierarchy is that colors become unreliable when binders are missing or insulation has deteriorated. We retain an unresolved identification as an exception until field evidence supports it. Guessing produces a clean-looking count with an uncertain circuit behind it, which is precisely the uncertainty a migration design must expose. ## Turn physical colors into usable assignment records The owner's cable count may describe assigned feeder pairs, local cable pairs or a range carried through a splice. Those meanings need a legend. We keep physical pair identity distinct from service assignment so an assignment change does not silently renumber the installed conductors or erase how an existing circuit reaches its terminal. ### Record the connection at both ends A splice record needs an incoming cable identity and pair reference connected to an outgoing cable identity and pair reference. The numbers may differ. An incoming pair 38 can legitimately connect to outgoing pair 12 if the owner's approved assignment says so; matching colors across that splice would produce the wrong connection. We show that example as a mapping, not as evidence of an installed splice. On each side, the record must resolve to a cable and its physical pair hierarchy. A terminal position belongs in its own field because terminal numbering can follow a different sequence from the cable's internal colors. Missing records also affect replacement design. Our [FTTH design work](/services/ftth-design) connects the replacement network layout to the service locations that the owner needs to migrate, while unresolved copper assignments remain visible for verification. A route can be ready for fiber construction even though a particular copper circuit still needs identification before cutover. ### Separate identity from condition A pair marked spare may be physically present but unsuitable for service. A disconnected circuit may still have a retained assignment. We keep service status separate from test results, and we retain the date and source of each observation so an old record does not appear to describe today's operating condition. Our preferred record is explicit about uncertainty. If a label says pair 38 but the verified continuity points elsewhere, preserve the label observation and the test result until the owner resolves the discrepancy. Overwriting one with the other removes useful evidence. The correction should explain which connection changed and which drawing revision now governs. For the wider inventory problem, our guide to [legacy copper network engineering](/blog/legacy-copper-network-engineering) explains why existing plant needs usable engineering records even while replacement is being planned. The color chart helps identify a conductor; the network record explains where its circuit goes and what depends on it. **Keep the original observation:** Photograph or transcribe an uncertain cable label before correcting the drawing. Preserve that observation beside the accepted correction so the next field visit can explain why the physical tag and the current record differ. ## Use copper records through splicing and fiber migration Splicing can destroy identification if binder control is lost before the record is captured. RUS paragraph (c)(5)(i) specifies loosely applied color-coded plastic tie wraps near the sheath to preserve binder identity. It also rejects twisted wire pigtails as binder identifiers because they can degrade transmission. Identification has to survive the work itself. The related *RUS specification for filled telephone cables*, 7 CFR 1755.390, in the CFR edition revised as of January 1, 2025, addresses cable construction and incorporates specified provisions of ANSI/ICEA S-84-608-1988. That incorporated edition is part of the RUS text; it should not be described as the newest ICEA publication. We use the cable's governing specification to interpret its markings. ### Preserve the copper circuit until cutover is accepted A fiber design should identify which service endpoint replaces the copper circuit and which unresolved assignments prevent a release. We recommend an explicit link between the copper circuit record and the replacement service record. A cable crossing the same route does not establish that relationship, because the fiber distribution architecture can serve endpoints differently. Pair counts do not translate directly into fiber counts. A 100-pair copper cable does not automatically require a 100-fiber replacement. Our [fiber strand count planning guide](/blog/fiber-strand-count-design-planning) addresses replacement capacity through network architecture and demand, rather than treating copper conductors as a fiber bill of materials. Fiber identification also uses a different convention. At the point where the replacement design assigns fibers, the [Fiber Color Code Chart](/tools/fiber-color-code-chart) provides a free ANSI/TIA-598 fiber color chart with a lookup from a fiber number to its buffer tube and fiber colors. Keep its results in the fiber record, separate from the copper tip/ring fields. ### Document what remains after migration Service migration and physical cable retirement are separate decisions. The owner should reconcile remaining assignments before releasing a cable for removal or recording it as abandoned in place under the applicable requirements. A successful fiber connection for one endpoint says nothing about another circuit that shares the copper sheath. We recommend retaining the last accepted copper assignment record with the migration evidence. It explains the former connectivity when a future excavation or maintenance visit encounters the remaining cable. Record the physical disposition explicitly. A system status of migrated should not be used to imply that the cable was removed from the route. The archive must also preserve unresolved branches. If a cable continues beyond the verified work area, show that boundary rather than extending an abandonment designation across an unexamined segment. Our design review separates what the field evidence establishes from what the owner still needs to confirm before authorizing further work. ## Choose the next step for your copper records **For active copper plant owners:** Reconcile pair identity at the splice or terminal before changing assignments. Start with the cable identifier and binder hierarchy, and keep test evidence attached to the affected circuit. Where records conflict, hold the specific assignment for resolution rather than treating the whole cable count as trustworthy. **For copper-to-fiber program managers:** Build the correspondence between existing circuits and replacement service endpoints before scheduling their cutovers. Keep the copper record available until the owner accepts the migration and decides the remaining cable's disposition. The 25-pair chart remains useful during that transition because maintenance work continues on the plant still carrying service. **For records and design teams:** Use separate fields for physical identification and assigned service. Define the notation before importing legacy sheets, and reject ambiguous labels into an exception queue instead of guessing at their meaning. That choice makes the unresolved work measurable without presenting an invented connection as an accepted design. Draftech International delivers turnkey telecom and power infrastructure, with engineering performed 100% in-house and full turnkey construction delivered by Draftech-managed subcontract crews. Our [partner and company information](/about) identifies the people accountable for that work. Send the route and available assignment records to [info@draftech.com](mailto:info@draftech.com) to discuss the engineering scope. For a route with uncertain copper assignments, we connect field findings to the replacement design so unresolved circuits remain visible through the handoff. When that record work supports a qualifying replacement route, our [first-route design offer](/free-design) covers the first 20,000 linear feet of engineering at no cost, from feasibility and field survey through permit approval. The owner reviews each request before Draftech commits the package, so the route's needs and the proposed engineering scope are considered before work begins. ## Frequently Asked Questions ### What are the colors in the 25 pair color code? The primary colors are white, red, black, yellow and violet; the secondary colors are blue, orange, green, brown and slate. Pair each primary color with the full secondary sequence before advancing to the next primary. That produces 25 combinations, starting with white/blue and ending with violet/slate, as shown in RUS Table 1 for telephone cable pairs. ### What color is pair 13? Pair 13 is black/green within a standard 25-pair group: black identifies tip and green identifies ring. In a larger cable, we also need the binder identity to locate the physical pair unambiguously. Local pair 13 in the second binder is cable pair 38, so a record should distinguish the local position from the cable pair number. ### Does a 25-pair telephone cable have 25 wires? A 25-pair cable has 50 insulated conductors because every pair contains a tip conductor and a ring conductor. The pair count describes the paired transmission paths, rather than the number of individual wires. We retain that distinction in cable schedules and termination records so a conductor quantity cannot be mistaken for the number of available pairs. ### How are binder groups identified above 25 pairs? The individual pair colors repeat inside each group, while colored binders identify the groups themselves. Under RUS Table 2, white/blue carries pairs 1 through 25 and white/orange carries 26 through 50. Larger cables can add super-unit identification, so we record every applicable level instead of relying on a pair color that repeats elsewhere in the cable. ### Can the copper color code determine replacement fiber counts? No direct conversion exists between 25 copper pairs and a replacement fiber count. Fiber capacity depends on the replacement network architecture and the services it must support, while copper records identify existing circuits that need migration. We use those records to preserve service correspondence, then assign fiber counts and fiber colors within the separate replacement design.