Skip to main content
Proof / Benchmark

Erase-time benchmarks

This page summarizes 2023 to 2026 MASAMUNE operating logs across mobile and storage workflows. These are not synthetic lab numbers. They are field logs cleaned with IQR-based outlier control.

3 yearsoperating logs
IQRoutlier control
7main device groups
NISTmethod comparison

Who this page helps

  • Teams estimating operational time before rollout
  • Organizations comparing HDD, SSD, and NVMe behavior
  • Operators who need a data-backed timing explanation for customers

How to read it

Field logsThese values come from live customer operations.
Outlier controlValues beyond 3×IQR were excluded.
Method mattersMedia type and erase method change the result dramatically.
Context: These numbers are references derived from real operating logs. Actual erase time still depends on media health, method, connectivity, and target condition.
Device groupAverageMedianMinMaxAvg speed
iPhone18m 28s15m 30s26s1h 8mN/A
iPad13m 56s11m 21s1m 20s47mN/A
Android8m 11s7m 48s44s25m 40sN/A
NVMe SSD16m 3s15m 25s1m 29s39m 37s344 MB/s
SATA SSD (M.2)12m 1s12m 36s3m 57s19m 21s280 MB/s
SATA SSD (2.5")25m 42s17m 48s2m 23s1h 47m344 MB/s
HDD2h 5m1h 34m22m8h 4m116 MB/s

NVMe is different

Hardware-driven NVMe paths behave very differently from HDD or SATA SSD workflows.

iPhone timing varies by model

IPSW size and generation matter, so flat timing assumptions are usually weak.

HDD scales with capacity

Write speed limits make larger HDDs much easier to estimate in hours.

Extreme times are a signal

Very long results often point to defective drives or unstable conditions.

Year-over-year trend

Device202320242025Trend
iPhone22m 15s19m 42s18m 28s17% faster
Android9m 30s8m 45s8m 11s14% faster
NVMe SSD19m 20s17m 10s16m 3s17% faster
HDD2h 30m2h 15m2h 5m17% faster

Method comparison

MethodAverageMedianMinMaxNIST level
Apple iOS (IPSW Restore)20m 37s15m 26s2m 50s5h 47mPurge
Android OS (Factory Reset)8m 21s7m 47s44s1h 1mClear
Zero Fill (1-pass)1h 52m18m 30s48s8h+Clear
ATA Secure Erase1m 10s1m 10s1m 10s1m 10sPurge
NVMe Crypto Erase<1s<1s<1s<1sPurge
DoD 5220.22-M (3-pass)5h 54m55m2m 24s24h+Purge

Capacity trend

Capacity bandAverageMedianTypical device
0–16 GB8m 48s7m 18sOlder smartphones
16–32 GB11m 45s9m 24sBudget smartphones
32–64 GB18m 54s13m 33sPhones, iPads
64–128 GB18m 48s12m 58siPhones, SSDs
128–256 GB1h 22m13m 12sSSDs, premium phones
256–512 GB55m 37s56m 26sSSDs
512 GB–1 TB2h 3m1h 56mSSDs, HDDs
1–2 TB3h 36m3h 31mHDDs
2–4 TB5h 28m5h 39mHDDs
4 TB+12h+12h+NAS / archive HDDs
We can map these timings to your own hardware mix.

If you already know your media mix and method expectations, we can frame the likely time profile before rollout.