Thirty percent of 240 is 72. Compact decimal form: 0.3 × 240 = 72. Because 240 is 24 tens, a single tenth is 24, and three tenths are 24 × 3 = 72. Partitioning 200 + 40 works too: thirty percent of 200 is 60, of 40 is 12, and 60 + 12 matches the same total.
Measured on the same 240 whole, everything outside that 30% band adds to 168, since 72 + 168 = 240. Retail receipts sometimes show 168 after a 30% markdown from 240 while tax is still quoted against the pre-cut figure—double-check which base the register uses before you reconcile.
The sections ahead spell out the arithmetic, park 72 next to 25%, a half, and an exact third on this scale, and sketch a few situations where 240 is minutes, seats, or throughput so the 72 stays anchored to this denominator.
Call 240 the full pool. A 30% assignment draws 72 units from it; the untouched remainder is 168. Swap the unit for litres, pixels, or tickets—the proportion stays fixed whenever the whole truly is 240.
Fraction view: 3/10 × 240 = 720/10 = 72. Factor view: 240 = 24 × 10 and 72 = 24 × 3, so you are taking three of the ten equal chunks sized 24.
Clock check: 240 minutes is exactly four hours. Thirty percent of that block is 72 minutes, a little more than an hour, with 168 minutes—two hours and 48 minutes—still unused inside the same four-hour window.
Step 1: Write 30% as a decimal: 30 ÷ 100 = 0.3.
Step 2: Multiply by 240: 0.3 × 240 = 72.
Same numbers as a single product: (30 ÷ 100) × 240 = 72 for this page.
Mental add-on: 5% of 240 is 12, so six five-percent notches yield 6 × 12 = 72 without touching 0.3.
Reference marks on 240 read 60 at 25%, 120 at 50%. Seventy-two should sit between them, a bit above the quarter—quick protection against a flipped digit in a spreadsheet.
Exact third: 240 ÷ 3 = 80. Thirty percent at 72 trails that third by 8. If a stakeholder rounds "a third of 240" in speech but the worksheet hard-codes 30%, expect 72 on paper, not 80.
Twelve-friendly structure: 240 = 12 × 20, and 72 = 12 × 6, so you can think in dozens if your inventory already ships that way.
Slide from 225: the base rose by 15, and 0.3 × 15 = 4.5, so the 30% slice grows from 67.5 to 72 when you step the whole from 225 to 240.
Chain from 10% and 20%: 10% → 24, 20% → 48, add another 24 for the last 10% to land on 72. That staircase matches how some people verify tiered discounts mentally.
Video render farm: A job queue budgets 240 GPU minutes for a nightly batch, and previews may consume 30% of that budget. Previews use 72 minutes; the remaining 168 minutes stay reserved for final-quality frames on the same cap.
Seminar room: A training space seats 240, and fire code sets aside 30% of seats for accessible positions. Seventy-two seats fall in the accessible pool; one hundred sixty-eight seats are treated as standard layout on that plan.
Throughput test: A service trial allows 240 requests per minute, and throttling documentation says 30% can burst to a partner integration. The integration may pull 72 requests in the measured minute; 168 remain for other clients under that quota.
Apiary harvest: A small yard projects 240 frames for extraction, and early nectar checks earmark 30% for a specialty label. Seventy-two frames feed that label run; one hundred sixty-eight frames stay on the general line for this harvest estimate.
30% of 240 is 72.
Triple 10% (24 × 3), or multiply 5% (12) by 6, or add 30% of 200 (60) to 30% of 40 (12).
Subtracting the 30% portion (72) leaves 168.
No. One-third of 240 is 80; 30% is 72.