Parallel conductor ampacity calculator
This parallel conductor ampacity calculator combines the allowable current capacity of two or more identical conductors used together for one high-current circuit.
Run — free
Enter the number of conductors, the ampacity already established for one conductor, and an optional adjustment factor. The result shows both the simple total and the adjusted combined ampacity in amperes. It is a transparent arithmetic aid for design comparisons and documentation, not a substitute for the electrical code, engineering judgment, equipment ratings, or approval by the authority having jurisdiction.
Start with a valid ampacity for one conductor
The most important input is the ampacity per conductor. That value should come from the electrical standard and edition that governs the installation, using the actual conductor material, size, insulation temperature rating, termination limitations, ambient temperature, raceway or cable arrangement, and other relevant conditions. Do not enter a catalog current, a breaker rating, or a convenient round number unless it truly represents the allowable ampacity of one installed conductor. The calculator deliberately does not contain a jurisdiction-specific ampacity table because table values and adjustment rules depend on the governing code and installation details. All conductors in the calculation are assumed to be identical and intended to share current as one parallel set. They should have matching electrical characteristics and installation conditions. If different sizes, materials, lengths, or terminations are mixed, simple multiplication can hide unequal current sharing and this calculator is not the right model. Establish the individual allowable ampacity first; then use this tool to combine it consistently.
Apply the count and adjustment factor
The unadjusted result is the conductor count multiplied by the ampacity of one conductor. For example, three identical conductors rated at 200 amperes each produce an unadjusted total of 600 amperes. The optional adjustment factor is then multiplied by that total. A factor of 0.8 retains eighty percent of the unadjusted value, while the default factor of 1 leaves it unchanged. Use this field only for a correction or derating multiplier that you have determined from the applicable rules. If your per-conductor ampacity already includes every required correction, leave the factor at 1 to avoid applying the same reduction twice. The factor is limited to values greater than zero and no greater than one because this input represents a reduction, not an increase. The output reports the inputs, unadjusted ampacity, adjusted combined ampacity, unit, and formula so the arithmetic can be reviewed or copied into a calculation record without guessing which convention was used.
Interpret the result within the complete circuit design
Combined ampacity is only one constraint in a parallel-conductor installation. The calculated value does not automatically become the permitted load, feeder rating, overcurrent device rating, or equipment rating. A complete design may also need to address minimum conductor sizes allowed for parallel operation, conductor grouping, current balance, neutral loading, continuous loads, terminal temperature limits, fault current, short-circuit protection, voltage drop, raceway fill, grounding and bonding, and local amendments. Compare the calculated ampacity with every other limiting component and use the lowest applicable limit. Also distinguish an ampacity adjustment from a continuous-load sizing rule: they answer different questions and should not be folded into one unexplained multiplier. The tool is most useful when the assumptions are already documented and a reviewer needs repeatable arithmetic. Keep the selected table reference, correction factors, conductor description, installation method, and governing code edition beside the result. Final selection and installation should be checked by a qualified electrical professional and accepted by the relevant authority.
What you can do with it
Compare parallel-set options
Compare how two, three, or four identical conductors change the available combined ampacity while keeping the source ampacity and assumptions visible.
Document a feeder calculation
Produce a clear unadjusted and adjusted total for a calculation sheet after the allowable ampacity and derating factor have been established.
Check repeated arithmetic
Automate the same deterministic multiplication across design scenarios without embedding jurisdiction-specific ampacity tables in a spreadsheet.
FAQ
What does the calculator compute?
It multiplies the number of identical parallel conductors by the allowable ampacity of one conductor and then by the optional adjustment factor.
Does it select a conductor size for me?
No. You must establish the allowable ampacity per conductor from the governing electrical code, installation conditions, and equipment limitations.
What adjustment factor should I enter?
Enter the applicable combined correction or derating multiplier that you have already determined. Leave it at 1 when the per-conductor ampacity is fully adjusted.
Can I use conductors of different sizes or materials?
No. This model assumes identical conductors under matching conditions. Mixed conductors require a more detailed current-sharing and code-compliance analysis.
Is the combined ampacity the breaker size?
Not necessarily. Overcurrent protection, continuous-load rules, equipment ratings, and other constraints must be evaluated separately under the applicable code.
What does the API cost?
Each API request costs $0.002; the same deterministic calculation can run free in the browser.
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/elec/parallel-conductors \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"conductor_count":3,"ampacity_per_conductor":200}'const res = await fetch("https://api.kit.forhosting.com/elec/parallel-conductors", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"conductor_count": 3,
"ampacity_per_conductor": 200
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/elec/parallel-conductors",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"conductor_count": 3,
"ampacity_per_conductor": 200
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/elec/parallel-conductors", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"conductor_count":3,"ampacity_per_conductor":200}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"conductor_count":3,"ampacity_per_conductor":200}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/elec/parallel-conductors", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"conductor_count": 3,
"ampacity_per_conductor": 200
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "elec.parallel_conductors",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |