Skip to content
Calcrivo

Evidence Transfer Time Calculator

Compare shipping evidence over the network against physical courier, including protocol efficiency and hash re-verification.

Inputs

GB
Mbps
%

TCP overhead, latency, encryption and contention

%
GB/s
hours
hours

Recommended Method

Network transfer — it lands sooner and keeps custody digital

Network Transfer Time

7.45hours

Effective Throughput

611Mbps

Re-verification Time

0.46hours

Network — End to End

8.41hours

Courier — End to End

20.46hours

Break-Even Volume

5,236GB

Step by step

  1. Values used

    Evidence to move = 2,000 GB; Link bandwidth available = 1,000 Mbps; Usable share of the link = 65 %; Encryption overhead = 6 %; Re-verification hash rate = 1.20 GB/s; Courier door-to-door time = 18 hours; Preparation and packaging time = 2 hours

  2. Evidence Transfer Time

    networkTime = size × 8 ÷ (bandwidth × usableShare × (1 − encryptionOverhead)); courierTime = preparation + doorToDoor. Both then pay size ÷ hashRate to re-verify on arrival.

  3. Break-even volume

    breakEvenVolume = effectiveTransferRate × courierElapsedTime — above this volume the courier wins.

  4. Recommended Method

    = Network transfer — it lands sooner and keeps custody digital

  5. Network Transfer Time

    = 7.45 hours

  6. Effective Throughput

    = 611 Mbps

  7. Re-verification Time

    = 0.46 hours

  8. Network — End to End

    = 8.41 hours

  9. Courier — End to End

    = 20.46 hours

How it works

A nominal gigabit link rarely delivers a gigabit: TCP windowing over a long fat pipe, encryption and other traffic typically leave 50–70% usable. Both routes end with the same obligation — re-hash on arrival and compare against the acquisition digest — so verification is added to each. The break-even volume is simply how much data the link could have moved during the courier's elapsed time. A courier is embarrassingly fast for large volumes, and 'never underestimate the bandwidth of a van full of disks' is still the right answer above a few terabytes on a shared WAN link.

Formulas

Evidence Transfer Time

networkTime = size × 8 ÷ (bandwidth × usableShare × (1 − encryptionOverhead)); courierTime = preparation + doorToDoor. Both then pay size ÷ hashRate to re-verify on arrival.

usableShare
Fraction of nominal bandwidth TCP actually achieves
encryptionOverhead
Cost of in-transit encryption
doorToDoor
Collection to delivery time for the courier

Break-even volume

breakEvenVolume = effectiveTransferRate × courierElapsedTime — above this volume the courier wins.

effectiveTransferRate
GB per hour actually achieved on the link
courierElapsedTime
Total courier time including packaging

Frequently Asked Questions

How is Evidence Transfer Time calculated?

networkTime = size × 8 ÷ (bandwidth × usableShare × (1 − encryptionOverhead)); courierTime = preparation + doorToDoor. Both then pay size ÷ hashRate to re-verify on arrival. A nominal gigabit link rarely delivers a gigabit: TCP windowing over a long fat pipe, encryption and other traffic typically leave 50–70% usable. Both routes end with the same obligation — re-hash on arrival and compare against the acquisition digest — so verification is added to each. The break-even volume is simply how much data the link could have moved during the courier's elapsed time.

Why does Evidence Transfer Time matter?

A courier is embarrassingly fast for large volumes, and 'never underestimate the bandwidth of a van full of disks' is still the right answer above a few terabytes on a shared WAN link.

What values do I need to enter?

This calculator takes 7 inputs: Evidence to move, Link bandwidth available, Usable share of the link, Encryption overhead, Re-verification hash rate, Courier door-to-door time, Preparation and packaging time. The pre-filled defaults are a realistic starting point — replace them with figures from your own environment for a result you can act on.

Does the courier route need extra controls?

Yes. Physical transfer needs tamper-evident packaging, encryption at rest on the shipped media, a signed custody form at each handover, and a hash comparison on arrival. The transfer time is the easy part; the custody paperwork is what gets challenged.

Why is preparation weighted differently for each route?

Network transfer needs staging and an upload script, which is a fraction of the effort of imaging to shippable media, packaging it, and completing custody documentation — so the model charges the network route a quarter of the preparation time.

You might also need