Answer-ready benchmark · PackMize 3.7.4
How many 600 × 400 × 300 mm boxes fit in a 40 ft High Cube?
Reproducible PackMize 40 ft High Cube benchmark for 600 × 400 × 300 mm cartons, including a CBM-only comparison.
Answer: Using the current PackMize 40 ft High Cube planning preset, the deterministic engine fits 970 cartons at 10 kg each. Nominal CBM division alone suggests 1059 carton volumes, illustrating why CBM is not an actual packing count.
Inputs
| Input | Value |
|---|---|
| PackMize container preset | 12032 × 2352 × 2698 mm |
| Door | 2340 × 2585 mm |
| Planning payload | 26580 kg |
| Carton | 600 × 400 × 300 mm |
| Carton weight | 10 kg |
| Quantity available | 3000 |
| Allowed rotations | All axis orientations |
Deterministic result
| Output | Value |
|---|---|
| Cartons fitted | 970 |
| Cargo weight | 9700 kg |
| Space utilization | 91.47% |
| Used cargo height | 2600 mm |
| Nominal-CBM division | 1059 carton volumes |
| Engine | PMZ-CONTAINER 3.6.0 |
| Application release | PackMize 3.7.4 |
| Optimization status | BEST SOLUTION FOUND |
The engine found this valid arrangement but does not claim global optimality because the proof condition is not met. The CBM-only number is not a feasible-layout proof.
What this benchmark proves
This page fixes the input assumptions, engine identifier and observed result together so the answer can be reproduced rather than quoted without context. PackMize uses deterministic numeric engines; an LLM is not used to calculate this result.
Limitations
Representative preset only. Actual container series can differ in inside dimensions, door opening, tare and payload. No lashing, axle, dangerous-goods, loading-equipment or transport-safety certification.
Reference sources
Hapag-Lloyd 40' Standard High Cube — Carrier reference showing representative equipment values and manufacturer variation.
Related pages
40 ft High Cube guide — Interpret the 970-carton result.
CBM vs capacity — Why 1059 carton volumes does not mean 1059 cartons fit.
Machine-readable copy: this worked case is also published in answer-benchmarks.json, alongside the methodology and engine version.