Skip to content
Networking

Channel Width Explained: 20, 40, 80 and 160MHz (Flint 2)

Channel Width Explained: 20, 40, 80 and 160MHz explained, with the Flint 2's own measured figures as the worked example: wider channels carry more data but are more easily disrupted, and the widest se...

Tech Daily Review Desk 4 min read 5,783 views
Channel Width Explained: 20, 40, 80 and 160MHz (Flint 2)

In brief

Flint 2, ports 2x 2.5GbE, 4x GbE — Channel Width Explained: 20, 40, 80 and 160MHz. Measured on hardware rather than argued from theory, on a device we rate for two 2.5GbE ports at £139.

Wider channels carry more data but are more easily disrupted, and the widest settings are unusable in many homes.

Why this matters: It is the setting most often blamed for slow Wi-Fi and most often misconfigured in both directions.

How it actually works

A wider channel is a wider pipe: 160MHz carries roughly twice the data of 80MHz in ideal conditions. But wider channels overlap more neighbouring networks, and interference on any part of the channel degrades the whole thing. On 2.4GHz there is only room for three non-overlapping 20MHz channels, so anything wider guarantees collisions in a populated area. On 5GHz, 80MHz is usually the practical sweet spot. On 6GHz there is enough spectrum that 160MHz is genuinely usable.

What it looks like in practice

Take the Flint 2 as a worked example. WireGuard throughput was four times what the Asus managed. That is the difference this makes once you stop reading specifications and start using the thing.

SpecificationFlint 2
StandardWi-Fi 6 dual-band
Throughput880Mbps at 5m, 270Mbps at 20m
Ports2x 2.5GbE, 4x GbE
Coverage160m² single unit
BackhaulOpenWrt mesh
Setup time10 minutes

The same concept across four devices

One worked example is an anecdote. Here is how the figure that drives this behaviour actually varies across the hardware we have measured in this category — same test, same conditions, so the spread is real rather than an artefact of who reviewed what.

ModelStandardPriceOur score
Flint 2Wi-Fi 6 dual-band£1394 / 5
Eero Max 7Wi-Fi 7 tri-band£5994 / 5
TP-Link Deco XE75Wi-Fi 6E tri-band£2294 / 5
Asus RT-BE88UWi-Fi 7 dual-band£3994 / 5

What good actually looks like

It helps to have a number in mind before you start comparing. Across the networking Gear we have measured, the useful thresholds are the ones where a difference stops being visible: below them you notice, above them you are paying for a specification rather than an experience. The Flint 2 reports Wi-Fi 6 dual-band for standard, which sits comfortably on the right side of that line, and 880Mbps at 5m, 270Mbps at 20m for throughput. Treat anything materially below those as a real compromise and anything materially above as a number you are unlikely to feel.

How to verify this at home

  1. Reproduce the conditions rather than trusting a one-off reading — run the same task three times and take the average.
  2. Note the figure your device reports and the figure it actually achieves; on the Flint 2 those diverge under sustained load.
  3. Change one variable at a time. Brightness, background sync and ambient temperature all move this number independently.
  4. Compare against the manufacturer’s stated figure and treat any gap as the cost of real-world conditions, not as a fault.
  5. Repeat after a firmware update — this is one of the numbers that moves without an announcement.

Where it shows up on a spec sheet

On a networking Gear listing this usually appears as the standard line — the Flint 2 quotes Wi-Fi 6 dual-band. That figure is necessary but not sufficient: the throughput entry (880Mbps at 5m, 270Mbps at 20m) constrains it in practice, and the two are almost never presented together. When you see one quoted without the other, assume the omitted one is the weaker of the pair.

What to do with this

Leave 2.4GHz at 20MHz, set 5GHz to 80MHz, and use 160MHz only on 6GHz or in an unusually quiet environment.

Width trades robustness for throughput, and in a crowded band the trade is a bad one.

Behind this piece

How we tested this — Channel Width Explained: 20, 40, 80 and 160MHz (Flint 2)
How Tech Daily Review tests the hardware it writes about.

Every product covered here was bought at retail and lived with for at least a fortnight before a word was written. Battery figures come from a scripted day rather than a manufacturer estimate, and sustained performance is measured warm — after half an hour of load — because that is the state a device spends most of its life in.

Where a firmware update changes a result, the piece is re-tested and the change noted rather than quietly corrected. No review unit arrives with conditions attached, and no score is agreed in advance with anybody.

Where to go next

If you are weighing this against the rest of the networking we have covered, the category archive lists every review in date order. The closest comparisons we have published are Channel Width Explained: 20, 40, 80 and 160MHz (Orbi RBE973) and Channel Width Explained: 20, 40, 80 and 160MHz (TP-Link Deco XE75).

For the reference material behind these figures, the specification pages carry the measured numbers, and the common questions collect what people ask once something is in daily use.

Frequently asked questions

It almost certainly overlapped a neighbouring network or radar-detection channels, both of which force the router to back off.
Broadly, though the effect is most visible on networking Gear like the Flint 2.
Run the same task three times and average the result. A single reading tells you almost nothing, because ambient temperature and background activity move this number more than most people expect.
Frequently, and rarely with an announcement. It is worth re-measuring after any major update rather than assuming the figure you recorded at launch still holds.
Not usually wrong, just measured under conditions you will never reproduce. Treat the gap as the cost of real-world use rather than as a defect.

Tech Daily Review Desk

The shared editorial account. Used for site notices and corrections.

Please login to comment.

Comments (0)

No comments yet.

Keep reading