Swell Sport · Practical guide
Comparing ice bath cooling-rate claims before buying
“Cools to” and “cools in” answer different buying questions. A minimum temperature describes an endpoint; a cooling rate describes a change over time. If you want a bath ready at a particular time, compare the evidence behind the rate rather than treating a headline endpoint as a timetable.

Separate three numbers on the product page
The Arctic U and Nordic Twin pages list a temperature range of 3°C to 42°C, a 1.0HP heating and cooling system, and approximate performance of 4–5°C per hour. Record these as seller-listed specifications, not independently measured results for your backyard. [1] [2]
Give the range, equipment rating and cooling-rate claim separate rows. Do not use the lower endpoint as a recommended immersion temperature, or turn the horsepower label into an electricity bill. The narrow question here is whether the published rate supports the preparation time you expect.
A worked calculation, with its assumption visible
For arithmetic only, suppose water starts at 25°C and the comparison endpoint is 15°C. That is a 10°C change. If a constant rate of 5°C per hour applied throughout, the calculation would be 10 ÷ 5 = 2 hours. At a constant 4°C per hour, it would be 10 ÷ 4 = 2.5 hours.
These are calculated scenarios, not observed cooling times, recommended bathing settings or a guarantee that either bath reaches that endpoint on that schedule. Write “constant-rate assumption” beside the result. Without evidence that the rate applies across the full change under the relevant conditions, the division alone cannot establish a ready-by time.
Ask for the conditions behind the rate
Build an evidence row with the tested bath and chiller version, water volume, starting and finishing temperatures, surrounding air conditions, lid position, elapsed time and source of the measurement. Ask whether the figure describes initial pull-down or an already-cold bath maintaining its setting. Keep those tasks separate in the comparison.
The same two product pages list approximate recommended fills of 250 litres for Arctic U and 650 litres for Nordic Twin. Because they list the same headline rate, ask which volume and configuration supported that rate for each model. The listings alone do not establish an identical test setup or an independently verified result. [1] [2]
Compare evidence of equal scope
Use one column per proposed system. Mark every field as supplied, not supplied or not comparable. If one result starts with warm tap water and another starts near its target, do not rank the second as faster merely because its elapsed time is shorter. The tests answer different questions.
Ask for an existing test record or a supplier-supervised demonstration using the intended equipment. You do not need to invent an extreme-temperature trial, change installation clearances or alter a chiller to investigate a sales claim. Keep the comparison within the approved operation of the supplied system.
Turn the comparison into a buying decision
Describe your actual requirement in plain terms: “I need to understand preparation time after a fresh fill,” or “I want evidence about maintaining a setting between planned uses.” Send that statement with the comparison sheet. A rate relevant to one requirement may leave the other unanswered.
If no relevant test conditions are supplied, leave preparation time unconfirmed in the purchase decision. That is more useful than presenting a neat but unsupported schedule. Compare verified features and the strength of the cooling evidence separately, and retain any specific written performance commitment with the accepted offer.
Your practical checklist
- Separate temperature endpoint, equipment rating and cooling rate.
- Label every calculated time with its assumptions.
- Compare the water volume and start/end temperatures.
- Ask whether evidence concerns fresh-fill cooling or maintenance.
Does a 3°C listing say how quickly the bath gets there?
No. An endpoint alone supplies no elapsed time. The cooling-rate evidence needs its own conditions. [1] [2]
Is the worked two-hour result a Swell performance promise?
No. It is arithmetic under an explicitly hypothetical constant-rate assumption, not a product test.

