# Teleporter data calculator > How much data would it take to beam you up? Count the data a fictional transporter would need to scan a person, and how long real links would take to send it. Estimate a fictional atom-by-atom body scan in yottabytes. Compare assumed bit budgets and link speeds, from home fibre to a laboratory record. - Page: https://how.box/transporter-data/ - Runs entirely in the browser. - License: HowToolbox's own text and data (titles, explanations, FAQs, tool descriptions and schemas, this file) are CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/); AI training and answers are welcome. Attribute "HowToolbox (how.box)" with a link to the page used. Third-party data keeps its own terms; the name and logo are not licensed. Publisher: HowToolbox, contact@how.box. Terms: https://how.box/about/terms/ ## Inputs Answer link: https://how.box/transporter-data/?atoms={atoms}&bits={bits}&speed={speed} - `atoms` (number 1 to 1e30): atoms. Example: `7e+27`. - `bits` (100, 1000, 8000 or 10000): Assumed classical bits per atom. Example: `1000`. - `speed` (1000000000, 100000000, 22900000000000000 or 6000000): Illustrative transfer rate. Example: `1000000000`. Example answer: https://how.box/transporter-data/?atoms=7e%2B27&bits=1000&speed=1000000000 The page computes the answer in the browser: read results from the agent tools below, not from the page HTML. ## Agent tools - `transporter_data_calculate`: Classical fictional body inventory: atoms times bits per atom, decimal bytes, ideal transfer years at bits per second, 13.8-billion-year universe ages, historical 2022 fixed-broadband traffic equivalents. - MCP, one POST to https://how.box/mcp: `{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"transporter_data_calculate","arguments":{"atoms":7e+27,"bits":"1000","speed":"1000000000"}}}` - GET: https://how.box/mcp/run/transporter_data_calculate?atoms=7e%2B27&bits=1000&speed=1000000000 ## How it works This fictional transporter stores a classical inventory of every atom's position and state: bits = atoms × bits per atom, bytes = bits ÷ 8 and seconds = bits ÷ link speed. A human body has about 7 × 10²⁷ atoms (BioNumbers). The 100, 1,000 and 10,000 bits per atom are illustrative budgets inspired by the chapter “Atoms or Bits?” in Lawrence Krauss's The Physics of Star Trek (1995), which suggests about 1 kB per atom; they are not measured encoding needs. At 1,000 bits per atom the body comes to 875,000 YB. At 1 Gbit/s, sending it takes about 2.22 × 10¹⁴ years. Decimal ZB and YB mean 10²¹ and 10²⁴ bytes; a year is 365.25 days and the universe is 13.8 billion years old. Scanning, error correction, rebuilding and travel time are left out. The fastest link in the examples is a 2023 laboratory record (NICT), not a service you can buy. The traffic comparison uses the ITU estimate of fixed-broadband traffic for 2022, not today's total. The 1 EB data centre is a round hypothetical size, not a claim about the largest real one. ## FAQ **Could this recreate a person?** No known technology can do this. A finite classical inventory does not specify an arbitrary quantum state. **Are these actual 5G and fibre speeds?** They are illustrative useful-throughput assumptions. Real services vary; the lab figure is an experimental aggregate. **Does the Mars link always run this fast?** No. Six Mbit/s is an MRO maximum; distance, antennas, scheduling and overhead reduce practical throughput. [NASA/JPL](https://www.jpl.nasa.gov/news/lasers-could-give-space-research-its-broadband-moment/). **Why vary bits per atom?** Precision and the states you choose to describe change the budget. None of these choices is a proven minimum. **Why use a hypothetical data centre?** There is no universal largest-centre storage capacity. Building area or electrical power cannot establish bytes stored. More: [HowToolbox index](https://how.box/llms.txt) · [Agent Skill](https://how.box/skill.md) · [agent terms](https://how.box/about/agents/)