DSL Speed Calculator
The formula
What the dsl sync prediction tells you
Copper-loop physics as a forecast: attenuation from the cabinet, then the technical roll-off curve of the chosen VDSL/G.fast/ADSL profile.
Calculation: Attenuation = km × dB/km (gauge-dependent); sync ≈ tech curve vs attenuation. Enter your inputs and every substitution is shown below the result.
Reading the result
Past ~60 dB the curve is a cliff — 400 extra meters of thin wire can cost more than the provider’s advertised tier.
Rules of thumb: Vectored VDSL2 delivers 100+ Mbps under ~0.5 km; G.fast needs ~150 m from cabinet.
Limitations and best practice
Inside-wiring quality (old in-house pairs, bridged taps) routinely costs 10–20 dB that this clean-loop model cannot see.
This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Frequently asked questions
Can I measure my attenuation?
Does bonding multiple pairs fix it?
Source & methodology
ITU G.993.2/G.9701 attenuation curves; UK/French operator loop-length vs sync datasets.
How DSL Speed works — and what your result really means
This page was written for one job: turning your own inputs into a defensible figure, with the working shown. DSL Speed is the kind of number people argue about from memory. This page ends that argument with arithmetic you can watch happen: enter your figures, get Predicted sync (down) in real time, and see every substitution printed below.
That makes documentation a feature. The steps block above exists so that the next engineer to read this page can verify not just the result but the reasoning — the difference between a number that gets acted on and one that gets argued with.
In plain terms, DSL Speed answers the question "Predicted sync (down)?". The measurement matters because it converts a situation that feels complicated — several inputs pulling in different directions — into a single number you can act on. Within Technology & Computing, Networks & Storage is the context where this figure is quoted most often, and professionals treat it as a first-pass screen rather than a verdict.
Every figure in the prose is generated by the engine rather than written beside it — the worked example resolves to predicted sync (down) = 37.4 Mbps on the default inputs, and the sensitivity section ranks the inputs that move the result — Loop length from the cabinet first, at ≈14.6 % of the headline for a ten-percent error either way in that input — which is the thread the rest of this guide pulls on.
Inside the DSL Speed calculation: formula and every input
One formula, published in full: Attenuation = km × dB/km (gauge-dependent); sync ≈ tech curve vs attenuation. Anything you can read, you can reproduce in a spreadsheet, and that reproducibility is the whole point of printing it rather than hiding it behind a button.
Loop length from the cabinet (km) (example value 6) is a measured number in the unit named by the label; the formula does not convert for you. Small measurement errors grow here: a length that is squared or cubed in the model magnifies a one-percent slip into a three-percent answer.
Service (example value VDSL2 vectoring) is a selector, not a measurement: the engine follows a different route for each option. If you are unsure what belongs in this field, look at the printed steps: the substitution shows exactly how the engine uses it.
Wire gauge (example value 0.4 mm (26 AWG)) is a branching choice rather than a figure you measure; the per-option effects are computed below. Replace the example with the figure from your own records — the tool recomputes instantly and the printed steps follow your numbers.
What each “Service” choice actually does: ADSL2+ → 1.5 Mbps · VDSL2 vectoring → 37.4 Mbps · G.fast → 90.0 Mbps That table is the honest answer to “does this option matter”, re-derived from the formula rather than hard-coded into page copy.
What each “Wire gauge” choice actually does: 0.4 mm (26 AWG) → 37.4 Mbps · 0.5 mm (24 AWG) → 50.0 Mbps These figures are computed from this engine, not estimated — switch the dropdown above and you will land on exactly these numbers.
A fully worked DSL Speed example
Abstract formulas are hard to trust, so here is the complete substitution using the default inputs, written the way an examiner would want it. Starting figures: Loop length from the cabinet (km), Service, Wire gauge. Run to the end, the predicted sync (down) resolves to 37.4 Mbps — Serviceable modern DSL on the bands this tool uses.
- Loop attenuation = 6.0 km × 13 dB/km = 78.0 dB
- VDSL2 holds 100+ to ~300 m then falls hard
- Model gives 37.4 Mbps down / 9.3 up
- At the modem cap the profile runs ~33 Mbps usable
Estimated attenuation — 78.0 dB. This is the number experienced users quote when the headline alone would mislead.
Predicted upstream — 9.4 Mbps. Compare it against the main result of 37.4 Mbps before drawing conclusions.
Attenuation budget left (100 dB cap) — 22.0 dB. This is the number experienced users quote when the headline alone would mislead.
Real throughput ≈ 0.87 of sync — 32.5 Mbps. Read next to the headline, this is the figure that shows the shape of the trade-off.
Re-running with your own figures is instant; re-running by hand once is the best way to know the tool is telling you the truth.
Scenario table: DSL Speed at ±10 % and ±20 % of the key input
Read this table as the practical error bar on the headline figure. It answers the question people actually have after seeing a single number: how wrong could this be if the main input is off by ten or twenty percent?
| Loop length from the cabinet setting | Predicted sync (down) |
|---|---|
| 80 % of the example value | 48.3 Mbps |
| 90 % of the example value | 42.9 Mbps |
| example inputs | 37.4 Mbps |
| 110 % of the example value | 31.9 Mbps |
| 120 % of the example value | 26.5 Mbps |
Across 5 settings of Loop length from the cabinet, the result spans 26.5 Mbps to 48.3 Mbps. A decision that only works at one row of this table is a decision waiting for an input to move. Reproduce it in the form above by editing Loop length from the cabinet alone; the substitution steps will follow your figures exactly.
The levers behind DSL Speed, ranked by effect
Generic advice says “it depends on your inputs”; this section says exactly how much. Each field was perturbed by ±10 % in isolation and the predicted sync (down) recomputed, so the ranking below is measured rather than asserted. For DSL Speed the ranking is measured rather than guessed, and it belongs to these defaults: shift the starting point and the order can shift with it.
- Loop length from the cabinet +10 % → DSL Speed = 31.9 Mbps · −10 % → 42.9 Mbps (the predicted sync (down) shifts ≈14.6 %)
Loop length from the cabinet is the dominant lever here: ten percent either way moves the result by about 14.6 %, from 31.9 Mbps to 42.9 Mbps. That is where a careless figure does the most damage, so check it against a source. Everything below that can stay approximate, which is a licence to stop chasing data that would not change the decision.
Interpreting the DSL Speed verdict
The value above only becomes useful the moment you know what it is being measured against. On the example inputs the band reads “Serviceable modern DSL”; your own figures place you on a different rung of the same ladder. Before treating the band as fact, note its width: ten percent either way on Loop length from the cabinet already spans 31.9 Mbps to 42.9 Mbps. The practical reading rules: read the band as a starting hypothesis, then test it: change the two dominant inputs by ten percent and see whether the verdict survives. Verdicts that survive stress are the ones worth acting on.
Set DSL Speed beside its neighbours and it usually plays a specific role: this figure establishes the size of something, and the neighbouring tools establish whether that size is acceptable. Skipping the first step makes the second one arbitrary.
How people get DSL Speed wrong
Inside-wiring quality (old in-house pairs, bridged taps) routinely costs 10–20 dB that this clean-loop model cannot see. This calculator gives an estimate based on standard formulas; it is not professional financial, medical, legal or engineering advice. Verify anything you plan to act on with a qualified professional and your own records.
Reporting the headline and quietly discarding Estimated attenuation. The companions are where the shape of the trade-off survives the rounding.
One mistake is specific to this engine: assuming every input matters equally. The computation above shows Loop length from the cabinet dominating — a careful figure there beats false precision everywhere else.
A final trap is presentation: reporting DSL Speed to more decimal places than the inputs support. The tool prints what the arithmetic gives; you should quote only what your least precise field justifies.
Six things to confirm before acting on DSL Speed
- Compare the result with one independent method or published benchmark.
- Note the date and the inputs beside the number so the figure can be audited later.
- Check Loop length from the cabinet before anything else: it is the measured dominant input, ≈14.6 % of DSL Speed per ten percent.
- State, in one sentence, which convention each rate, unit or period in the form is using.
- Recompute once with the dominant input deliberately set low, and see whether the decision changes.
- Confirm the answer against one independent method or published benchmark for DSL Speed.
How to use the DSL Speed tool properly
The tool does the arithmetic; the routine below is what makes the arithmetic trustworthy. Five steps, a minute total — and afterwards you will know not just what the number is, but which assumption produced it.
Step 1 — gather before you type. DSL Speed depends on loop length from the cabinet (km), service, wire gauge. Collect them from a source document — a statement, a report, an invoice, a log — rather than from memory, because recalled inputs are the single largest cause of wrong results. Half of a good calculation is knowing which input you would hate to be wrong about.
Step 2 — enter the conservative case first. Resist the flattering scenario. Type the inputs you would defend in front of a sceptical reader, read the Predicted sync (down) (37.4 Mbps for the example values), and note the verdict band. Repeating a calculation with the same numbers proves only that the arithmetic is reliable — which is worth knowing.
Step 3 — play with the inputs on purpose. Ten percent up, ten percent down, one field at a time. Within a few minutes you will know this calculation better than most people who quote its results. Compare the calculation to the rough guess you arrived with, and ask why they differ.
Step 4 — compute a corridor, not a point. Three runs — worst, likely, best — turn DSL Speed from a snapshot into a range. Plan against the pessimistic end and treat the optimistic end as the upside story. Note the assumption you are least sure about; that is where the real risk lives.
Step 5 — schedule the next run. In Technology & Computing the inputs drift quietly. Put a reminder a quarter out, re-enter the same fields, and read the change rather than the level. Say the answer out loud before you save it; if it sounds wrong, the model did not change, your understanding did.
The real-world conversations DSL Speed settles
Technology & Computing arguments end at arithmetic or they do not end. DSL Speed is the arithmetic: 37.4 Mbps on the example inputs, reproducible by anyone who types the same numbers. Precision is a promise you make about your data; make sure your inputs can keep it.
Used properly this is a five-minute filter that saves weeks. Compute DSL Speed, reject what fails, and only then bring in the expensive analysis for the survivors. Compare the calculation to the rough guess you arrived with, and ask why they differ.
There is a personal-administration use people overlook: periodic self-checking. DSL Speed quietly drifts as life changes — rates move, bodies change, costs compound — and re-running it a few times a year catches drift while correction is still cheap. When two sources disagree, it is almost never the arithmetic that differs.
People also ask about DSL Speed
What affects DSL Speed the most?
The short answer: Loop length from the cabinet. The longer answer is the sensitivity table on this page, where every numeric input was probed by ten percent and the predicted sync (down) recalculated — Loop length from the cabinet moved it furthest, by roughly 14.6 % (31.9 Mbps to 42.9 Mbps).
How much does the “Service” choice change the answer?
Across every option this tool offers, the predicted sync (down) ranges from 1.5 Mbps (ADSL2+) to 90.0 Mbps (G.fast) with all other inputs held at their example values. The per-option table is printed in the inputs section — this is a decision that genuinely moves the number, not a cosmetic dropdown.
What is a typical DSL Speed?
There is no honest universal average for DSL Speed, but there is a reference point: the defaults on this page produce 37.4 Mbps (Serviceable modern DSL). Replace the inputs with your own and compare — that comparison is the useful meaning of “typical”.
How do I calculate DSL Speed by hand?
Use the stated model — Attenuation = km × dB/km (gauge-dependent); sync ≈ tech curve vs attenuation — and substitute in the order the tool prints (it starts from Loop attenuation = 6.0 km × 13 dB/km = 78.0 dB). On the example inputs the hand route lands on 37.4 Mbps, exactly what the calculator shows. A spreadsheet reproduces it in two or three cells; doing it once by hand is what makes the automated answer trustworthy.
What happens to DSL Speed if loop length from the cabinet changes by 10 %?
The engine was re-run with that field moved by ten percent while everything else stayed fixed: the predicted sync (down) goes across 31.9 Mbps to 42.9 Mbps, a swing of roughly 14.6 % around the 37.4 Mbps baseline. That ratio is the practical definition of how much this input matters.
Is the DSL Speed result of 37.4 Mbps good or bad?
Good and bad are comparisons, so the honest test is three questions: where does your own DSL Speed sit against the 37.4 Mbps reference above, how far would a plausible input error move it (≈14.6 % per ten percent on Loop length from the cabinet), and what does the alternative option compute to?
What affects DSL Speed the most?
Sensitivity depends on where you start, but the inputs Loop length from the cabinet (km) and Service typically move DSL Speed further than the rest because they enter the formula multiplicatively. If you can only measure two things well, measure those and hold the others at conservative defaults.
Is DSL Speed accurate?
The arithmetic is exact: Attenuation = km × dB/km (gauge-dependent); sync ≈ tech curve vs attenuation is evaluated with full floating-point precision and every substitution is printed in the worked example. What limits accuracy is input quality and the model’s assumptions, so treat the 37.4 Mbps result as the correct answer to the question you typed — and check the assumptions section before acting on it.
Can I measure my attenuation?
Yes — the modem status page prints it; feed that number back in as ground truth and the model calibrates instantly.
Does bonding multiple pairs fix it?
For legacy copper, ITU G.bond existed but deployments are rare; the real-world fix remains fibre to the premises.
Does this DSL Speed tool store my numbers?
No. The entire calculation runs in your browser session; nothing entered above is transmitted or saved, which is the correct behaviour for sensitive Technology & Computing figures and the reason you can re-run this page as often as you like.
What the labels on this page mean
- Estimated attenuation
- 78.0 dB for the DSL Speed worked case; it sits next to the main result because it carries context the headline leaves out.
- Predicted upstream
- 9.4 Mbps for the DSL Speed worked case; it sits next to the main result because it carries context the headline leaves out.
- Attenuation budget left (100 dB cap)
- 22.0 dB in the default DSL Speed calculation — one of the secondary figures an experienced reader checks before trusting the primary number.
- Predicted sync (down)
- The primary output of this tool: 37.4 Mbps for the default inputs, computed exactly from Attenuation = km × dB/km (gauge-dependent); sync ≈ tech curve vs attenuation.
- Worked example
- Every substitution in order, from the example inputs to 37.4 Mbps — the audit trail for the headline figure.
- Verdict band
- The interpretation attached to a result (“Serviceable modern DSL” on these inputs), which turns a bare number into a position on a scale.
- Sensitivity (±10 %)
- How far the DSL Speed moves when a single input is nudged ten percent either way; the ranked list on this page is computed live from this engine.
Where the DSL Speed model comes from
The model is published arithmetic implemented exactly as written: Attenuation = km × dB/km (gauge-dependent); sync ≈ tech curve vs attenuation. Source of record: ITU G.993.2/G.9701 attenuation curves; UK/French operator loop-length vs sync datasets. Any other implementation of this model should return the same figure for the same inputs. If one does not, the difference is in its assumptions — which this page prints and that one probably does not.
This page is an estimation aid, not professional advice. The design rule is simple: two people entering identical figures must get identical answers. The design constraint was set by usefulness rather than by comfort: an estimate you can interrogate beats an answer you have to trust.
After the number: what to do with it
Re-run the calculation with your own figures, stress the two most sensitive inputs by ±10 %, and only then act on the result.
The audience here is people who need one trustworthy number before their next decision. Everything you need to defend the result — formula, substitution, sensitivity, source — is printed above, so the only remaining variable is the honesty of your inputs.