Signal Propagation Delay Calculator

Calculate

Enter the one-way signal travel distance

Select the unit for the path length input

Choose how you will enter propagation velocity

Enter velocity as fraction of c (e.g. 0.66) or in m/s — depending on the mode selected above

Overview

How much time does a signal actually need to cross a cable, a fiber link, or a long wire run?

This calculator gives you a clean answer from two numbers: path length and propagation velocity. Enter the distance in meters, kilometers, feet, or miles, and the signal speed as either meters per second or a fraction of the speed of light. The result is the one-way geometric propagation delay in nanoseconds, microseconds, or milliseconds — alongside the propagation speed expressed as a percentage of c.

This kind of quick estimate is useful before you build a full timing budget. It works for cable runs in control and automation systems, long fiber links in communications networks, clock distribution paths, trigger lines in protection relays, and any other path where distance and signal speed both matter for timing.

The key scope limit: this calculator includes only the geometric delay from path length and propagation speed. It does not include device delay, connector delay, repeater delay, protocol overhead, or switching latency. For a complete timing analysis you still need the full end-to-end budget — but this gives you the propagation term quickly.

How to Use This Calculator

  1. Enter the path length — type the one-way signal travel distance in the path length field.

  2. Select the length unit — choose m, km, ft, or mi depending on how you measured the path.

  3. Select the velocity input mode — choose Fraction of c if you know the velocity factor (e.g. 0.66), or m/s if you have the actual speed.

  4. Enter the propagation velocity — type 0.66 for 66% of the speed of light in fraction mode, or the actual speed in m/s for that mode.

  5. Click Calculate — get one-way delay in ns, µs, and ms, plus propagation speed as a percentage of c.

  6. Review the result and status — check which delay band the result falls in, then compare it with the full timing budget of your system.

Path length must be greater than zero. Propagation velocity must be greater than zero and cannot exceed the speed of light (299 792 458 m/s or 1.0 as a fraction of c). Fraction of c must be between 0 and 1.

Inputs & Outputs

Inputs

  • Path Length
  • Length Unit — Options: ft, mi, m, km
  • Velocity Input Mode — Options: Fraction of c (e.g. 0.66), m/s (e.g. 200000000)
  • Propagation Velocity

Outputs

  • One-Way Delay (ns)
  • Propagation Speed (% of c)

Formula

Calculator Formula

One-way propagation delay equals path length divided by propagation velocity. Here is the full step-by-step model.

Step 1: Convert path length to meters

If unit = m:   Length_m = Length
If unit = km:  Length_m = Length × 1000
If unit = ft:  Length_m = Length × 0.3048
If unit = mi:  Length_m = Length × 1609.344

Step 2: Convert propagation velocity to meters per second

If mode = m/s:          Velocity_mps = Velocity
If mode = fraction of c: Velocity_mps = Velocity × 299 792 458

Step 3: Calculate one-way propagation delay

Delay_s = Length_m / Velocity_mps

Step 4: Convert to readable time units

Delay_ns = Delay_s × 1 000 000 000
Delay_µs = Delay_s × 1 000 000
Delay_ms = Delay_s × 1 000

Step 5: Express propagation speed as a percentage of c

Velocity_% = (Velocity_mps / 299 792 458) × 100

Variables

Variable Meaning
Length_m Signal travel distance in meters
Velocity_mps Propagation velocity in meters per second
Delay_s One-way propagation delay in seconds
Delay_ns One-way delay in nanoseconds
Delay_µs One-way delay in microseconds
Delay_ms One-way delay in milliseconds
Velocity_% Propagation speed relative to the speed of light

Decision Model

The result is classified by one-way delay.

Status Condition
VERY SHORT Delay < 10 ns
SHORT 10 ns to < 1 µs
MODERATE 1 µs to < 100 µs
LONG 100 µs to < 10 ms
VERY LONG 10 ms or more

Key relationships:

  • Delay is proportional to path length. Double the length, double the delay.
  • Delay is inversely proportional to velocity. Double the speed, halve the delay.
  • This is a one-way geometric delay only. It does not include electronics, connectors, switching, protocol, or software timing.

What is Signal Propagation Delay

Signal propagation delay is the time a signal needs to travel from one point to another through a physical path. In a cable, fiber link, or wire run, that time depends on two things: how long the path is, and how fast the signal moves through the medium. The result is a pure geometric delay — it does not include any processing, switching, protocol, or device timing.

This calculator computes that one-way geometric delay from path length and propagation velocity. You enter the distance and the signal speed, and it returns the delay in the most readable time unit: nanoseconds for short runs, microseconds for medium-length links, milliseconds for long paths. It also shows the propagation speed as a percentage of the speed of light, which helps cross-check whether the velocity factor is realistic for the medium.

The result is a first-pass screening estimate, not a complete timing analysis. Real systems add additional delay from device electronics, connectors, repeaters, switches, serialization logic, protocol stack, and software. All of those are outside the scope of a pure propagation-delay estimate. What this calculator provides is the propagation term — the minimum possible transit time set by physics and path length.

Use this when you need a fast, clean geometric reference before building the full end-to-end timing budget.

Key Facts

  • A 200 m cable gives twice the delay of a 100 m cable at the same propagation speed.
  • Doubling the propagation velocity cuts the delay in half. Halving it doubles the delay.
  • Below 10 ns is very short in this model, but can still matter in DDR, PCIe, multi-gigabit, or precision trigger paths.
  • Delays close to 1 µs already deserve attention in many timing, synchronization, and protection tasks.
  • At about 0.66c, 10 ns is only a few meters of cable, 1 µs is roughly 200 m, and 10 ms is roughly 2 000 km.
  • A velocity of 100% of c is mathematically valid in this model, but real physical media are always somewhat slower.
  • Copper cables commonly run at about 0.6–0.8c depending on construction. Fiber typically runs near 0.67–0.70c.

Applications

  • Quick cable and path timing checks in control, automation, and protection systems.
  • First-pass delay estimation for trigger paths, clock distribution networks, and synchronization links.
  • Basic review of long fiber, coax, or twisted-pair links before full timing-budget work.
  • Comparing different media assumptions by changing the velocity factor input.
  • Educational checks on how path distance and propagation speed jointly affect one-way timing.

Example Calculation

Example Calculation

This example uses a realistic cable-style velocity factor of 0.66c and a 100 m path — a result that engineers can easily visualize in the sub-microsecond range. A velocity of 0.66c is typical for many copper twisted-pair and coax cables.

Given:

  • Path Length = 100 m
  • Velocity = 0.66 (fraction of c)

Step 1: Length is already in meters

Length_m = 100 m

Step 2: Convert velocity to m/s

Velocity_mps = 0.66 × 299 792 458 ≈ 197 863 022 m/s

Step 3: Calculate one-way delay

Delay_s = 100 / 197 863 022 ≈ 5.05 × 10⁻⁷ s

Step 4: Convert to readable units

Delay_ns ≈ 505 ns
Delay_µs ≈ 0.505 µs
Delay_ms ≈ 0.0005 ms

Step 5: Propagation speed as % of c

Velocity_% = 66.0%

Results:

  • One-Way Delay = 505 ns = 0.505 µs
  • Propagation Speed = 66.0% of c
  • Status = SHORT

Interpretation: This is a short propagation delay, but it is already large enough to matter in synchronization, trigger, or high-speed timing work. A cable run of only 100 m is not always timing-negligible once the budget gets tight.

Standards & References

Limitations

  • This calculator estimates one-way geometric propagation delay from path length and propagation velocity only.
  • It does not include electronics delay, connector delay, repeater delay, switch delay, serialization delay, queuing delay, or protocol overhead.
  • It does not determine whether a specific bus, interface, or communications system will function correctly within a timing budget.
  • It does not replace full timing-budget analysis, signal-integrity simulation, or field measurement.
  • The model has no separate Metric vs Imperial physics — both input systems are converted to meters internally before computing.

Common Mistakes to Avoid

  • Forgetting that this result is one-way delay only. Round-trip latency will be approximately twice as large.
  • Entering a velocity factor that is unrealistically high or low for the actual medium — that can shift the result significantly.
  • Assuming short distance always means negligible timing impact. In a 10 Gbit/s link or a protection relay, even 10–50 ns can matter.
  • Treating propagation delay as total system latency. It is only one term in the full timing chain.
  • Mixing up length units. Miles, feet, meters, and kilometers all convert correctly here, but selecting the wrong unit changes the result dramatically.

Frequently Asked Questions

What does this calculator do?
It calculates one-way signal propagation delay from path length and propagation velocity. Enter the distance and speed, and it returns the geometric delay in nanoseconds, microseconds, and milliseconds, plus the speed as a percentage of c.
What is the basic formula?
One-way delay equals path length divided by propagation velocity. All length inputs are converted to meters and all velocity inputs to meters per second before the division is performed.
Is this one-way delay or round-trip delay?
It is one-way delay only. Round-trip latency — such as a ping response — will be roughly twice the one-way propagation delay, plus any device processing time.
Can I enter velocity as a fraction of the speed of light?
Yes. Select the fraction of c mode and enter a value between 0 and 1. The calculator converts that fraction to meters per second internally. For example, 0.66 means the signal travels at 66% of the speed of light.
Why can the result matter even when the delay looks small?
Because fast digital, synchronization, trigger, and protection systems can be sensitive even to nanosecond- or microsecond-scale delay. Always compare the result against the actual timing budget of your system, not just the raw number.
What does 0.66c mean?
It means the signal is assumed to travel at 66% of the speed of light. This is a typical velocity factor for many copper twisted-pair and coax cables. Actual values vary by cable construction and should be confirmed from the manufacturer's datasheet.
Can I use imperial length units like feet or miles?
Yes. Feet and miles are converted internally to meters before the delay is calculated. Select ft or mi from the length unit dropdown and the conversion is handled automatically.
Does this calculator include switch, repeater, or protocol delay?
No. It calculates geometric one-way propagation delay from distance and speed only. Switch delay, repeater delay, connector delay, protocol overhead, serialization delay, and software latency are not included.
My cable is 10 m long. Do I really need to care about 50 ns delay?
It depends on the system. For a human pressing a button, no. For a 10 Gbit/s interface, a protection relay, or a precision trigger path, a 50 ns delay can be significant. Always compare the result against the timing budget of the specific application.

Frequently Used Together

Engineers often use these calculators in combination for complete project workflows:

Every Electrical Formula. One Free Sheet.

NEC calcs, motor sizing & code coordination — one printable page.

  • Instantly check voltage drop, ampacity & motor current
  • Catch the 7 wiring errors that fail code inspections
  • 12 design checks to run before submitting drawings

No spam. Unsubscribe any time.