InHand CR602 Review: Portable 5G

By Peter Green

Every few months a portable 5G router turns up that is a bit better than the last one, and the marketing copy reaches for the same three words. Fast. Flexible. Future-proof.

The InHand CR602 is better than most, and I want to be clear about that up front. It is a properly specified bit of kit. But there are three things in the datasheet that InHand does not draw your attention to, and one of them will determine whether you can legally sell this thing in Britain at all.

Let us start with what it actually is.

What the CR602 is

It is a portable indoor 5G router with a battery. It takes a cellular connection and turns it into Wi-Fi and wired Ethernet for a small office, a temporary site or a pop-up.

Where it separates itself from the MiFi pack is the networking. Two 2.5 Gigabit Ethernet ports, both switchable between WAN and LAN. VLANs, DHCP snooping, static routing, policy routing, traffic shaping, a three-layer firewall, SNAT and DNAT, IPsec and L2TP VPN. Cloud management through InCloud Manager with zero-touch deployment and batch upgrades.

That is a router feature set, not a hotspot feature set. A consumer MiFi does not give you an uplink priority table you can drag rows around in.

Verified specification

Three things worth reading twice

1. That certification list has no CE and no UKCA on it

2. It is Wi-Fi 7 without the 6 GHz band

Wi-Fi 7’s headline capability is 320 MHz channels, and 320 MHz channels live in the 6 GHz band. The CR602 runs 2.4 GHz and 5.8 GHz only.

So you get Wi-Fi 7’s other improvements, 4K-QAM and the efficiency gains, on 2.4 and 5 GHz spectrum. That is a real upgrade over Wi-Fi 6. It is not the Wi-Fi 7 the marketing image in your head is showing you.

The 3000 Mbps figure is the aggregate PHY rate across both bands. Actual device throughput is 1 Gbps. Which brings us neatly to the next one.

3. 7.01 Gbps is a modem number, not a router number

The 7.01 Gbps peak is what the modem chipset can theoretically achieve under laboratory conditions with carrier aggregation across spectrum no UK operator will give you. InHand’s own specification lists device throughput at 1 Gbps.

1 Gbps is still excellent. It is also seven times smaller than the number on the front of the brochure. Plan your capacity against the 1 Gbps figure and the 32 Wi-Fi client ceiling, not the 7.01.

The triple SIM architecture, and what it actually buys you

Two nano SIM slots plus an eSIM. InHand supports multi-SIM switching and automatic redial, so the practical benefit is straightforward.

You might put an EE SIM in slot one and a Vodafone SIM in slot two, with a third profile sitting on the eSIM. If EE has a bad afternoon, the device moves. For a temporary office or a business continuity link, that is exactly the behaviour you want.

The subtler benefit is procurement flexibility. A customer-owned SIM in slot one, a managed IoT SIM in slot two, no screwdriver required to change your mind later.

The eSIM explainer, because “eSIM” means four different things

An eSIM is not a small SIM. That is the single most common misunderstanding in this business, and vendors are not in a hurry to correct it.

The physical component is an eUICC, an embedded Universal Integrated Circuit Card. It is soldered to the board. What makes it interesting is not its size but its capacity to hold multiple operator profiles and to have new ones downloaded to it over the air.

So far, so good. The complication is that there are three separate GSMA specifications governing how those profiles get onto the chip, and they are not interchangeable.

Why SGP.22 is the wrong tool for an unattended fleet

SGP.22 works beautifully on a phone. You scan a QR code, you tap accept, you are on a new network. The whole flow assumes a Local Profile Assistant, a screen and a human being.

Now put that device on a pole in Northumberland. There is no screen. There is nobody there. The flow breaks down, and you are back to sending an engineer in a van, which is the exact cost that eSIM was sold to you as eliminating.

SGP.32 fixes this. It replaces the LPA with an IoT Profile Assistant, and it introduces the eSIM IoT Manager (eIM), a backend that can push profile operations to devices asynchronously. The eIM assumes user intent rather than waiting for it. Profiles get downloaded, enabled, disabled and deleted across an entire estate without anyone leaving the office.

It also brings a rollback mechanism. If a new profile fails to attach within a defined window, the IPA reverts to the last working one. Anyone who has ever bricked a remote site with a bad APN change will understand why that matters.

So which one is in the CR602?

For the CR602’s actual target market, that is fine. This is a portable router. There is a person holding it. There is a web interface at 192.168.2.1 and somebody to log into it. SGP.22 is the appropriate specification for a device that has a human attached.

The problem only appears if you read “eSIM” on a portable router datasheet and extrapolate it to a fleet of 5,000 unattended assets. Different device class, different specification, different conversation entirely.

If you are specifying for scale, ask the vendor these four questions and do not accept “it has eSIM” as an answer to any of them:

• Which GSMA specification does the eUICC implement, SGP.02, SGP.22 or SGP.32?
• If SGP.32, is the IPA on the device (IPAd) or in the eUICC (IPAe)?
• Which eIM platforms has it been tested against?
• Is full remote profile download supported, or only preloaded profiles that can be switched between?

That last one catches people out constantly. A device that ships with three profiles already on it and lets you toggle between them is not doing remote SIM provisioning. It is doing a multi-IMSI impression of it.

The SIM matters more than the router

Here is the thing that fifteen years of watching deployments go wrong has taught me. The router is rarely the weak link. The SIM usually is.

A single-network SIM connects to one operator. When that operator has a bad day, and they all have bad days, your site is dark. It does not matter that you paid for Wi-Fi 7 and 2.5 Gigabit Ethernet. The uplink is gone.

A roaming SIM behaves differently. It can attach to multiple networks, so when one degrades, the device has somewhere else to go. Combine that with the CR602’s two physical slots and you have genuine diversity rather than the illusion of it.

The pairing that actually makes sense here is a roaming SIM in slot one and a fixed-network SIM in slot two. Multi-network resilience as the primary, a known-quantity fallback behind it. Leave the eSIM for whatever the customer brings to the party.

Where it fits, and where it does not

The temperature rating is doing quiet work in this section. -10 °C to +40 °C, IP30, plastic enclosure, fanless. IP30 means it is protected against solid objects over 2.5 mm and nothing at all against water.

Good fits

Poor fits

• Outdoor mounting. IP30 and a plastic case. It is an indoor product.
• Vehicles. No DC input, no ignition sensing, no vibration rating, no M12 connectors, and a +40 °C ceiling that a parked van in July will laugh at.
• Unattended industrial deployment. No DIN rail, no serial ports, no Modbus or DNP3, no wide temperature range. InHand make an IR-series for that, and it exists for a reason.
• Anything over 32 Wi-Fi clients. The 128 figure is the device total across all interfaces. Wi-Fi caps at 32.
• Large unattended fleets needing remote profile changes. See the SGP.32 discussion above.

Verdict

Further reading

Specifications verified against InHand’s published CR602 product documentation, July 2026. IoT UK has no commercial relationship with InHand Networks. Specifications and certifications change. Confirm current details with the vendor before purchase.