Sizing a 4G router connection for a remote CCTV site means working backward from the video traffic that actually has to leave the location. Start with camera bitrate, calculate how many streams may be active together, convert that traffic into monthly data use, and then prove that the real cellular uplink can carry it.
The router comes later. A higher-spec cellular router cannot compensate for an overloaded mobile cell, an unrealistic camera bitrate assumption, or a data plan calculated from camera count alone.
The practical goal is to answer one question before deployment: can this CCTV workload cross this 4G connection with enough operating margin to remain usable when the site actually needs video?
What are you actually sizing?
Follow the path that video takes from the camera to the remote monitoring system. Each stage answers a different part of the sizing problem.
The sizing rule
Do not begin with “How many cameras can this router support?” Eight cameras recording locally and sending two occasional remote streams create a very different cellular workload from eight cameras continuously uploading video. Define the traffic first; select the hardware second.
Use the stream that actually leaves the site.
Model normal use and the busiest credible event.
Convert bitrate and active time into monthly data.
Test real upstream capacity at the final location.
Match SIM, Ethernet, PoE and redundancy needs.
1. Start with the bitrate of the stream that actually leaves the site
Resolution alone does not define CCTV bandwidth. Cameras with the same nominal resolution can generate different traffic because frame rate, codec settings, image quality, scene movement and the selected stream profile all affect encoded bitrate.
The number that matters is the configured or measured bitrate of the stream transmitted through the cellular connection.
Eight cameras can still create a two-stream cellular load
A construction site may record all eight cameras to a local NVR but normally send only two remote live views. In that case, the normal 4G load is based on those two streams.
The peak calculation should still ask what happens during an alarm, playback request or operator investigation when additional video leaves the site.
Once the camera workload is defined, the next step is to compare the site requirement with a suitable 4G router architecture, including the required cellular capability, Ethernet layout, SIM strategy and PoE arrangement. The hardware decision should follow the measured CCTV workload rather than theoretical LTE speed alone.
2. Calculate simultaneous upstream traffic
For remote CCTV, the uplink is usually the critical direction because video is travelling from the site toward a VMS, cloud platform or monitoring centre.
The useful planning number is not simply the daily average. It is the highest realistic combination of streams that may need to leave the site at the same time.
Four active cameras at 1.5 Mbps each
Better when
The real site test can sustain the normal load and the busiest credible camera condition while still leaving useful upstream margin.
Avoid accepting
A design where calculated camera traffic and measured uplink are almost identical. It may work during one short test but fail when radio or network conditions change.
3. Convert camera bitrate into monthly 4G data use
Bandwidth answers whether the connection can carry the video at a particular moment. The SIM data plan answers a different question: how much traffic will cross the cellular network during the billing period?
This is why continuous remote recording can create a substantial monthly allowance even when the individual camera bitrate looks modest. Four continuous 1.5 Mbps streams would represent roughly 1.94 TB over 30 days.
The same cameras can use far less cellular data when recording stays local and the 4G connection is used mainly for alarms, selected playback or operator live viewing.
4. Compare calculated load with the real cellular uplink
A correct CCTV calculation can still fail in the field because cellular throughput is not fixed. Signal quality, network loading and the final installation position all influence the upstream capacity available to the cameras.
Good fit
Video remains stable during realistic peak traffic and repeated tests show useful capacity beyond the calculated camera load.
Poor fit
The connection only passes a brief speed test or becomes unstable as several camera streams start transmitting together.
If the link fails here, buying a router with a higher theoretical LTE specification does not automatically solve the problem. First establish whether the bottleneck is camera traffic, installation conditions or the mobile network itself.
5. Reproduce the real CCTV workload before the site goes live
A generic mobile speed test is useful as a baseline, but the final acceptance test should reproduce the traffic that the cameras will actually create.
Predeployment CCTV test
- Use the production camera profile. Confirm the bitrate and frame rate intended for the live installation.
- Open the normal number of remote streams. Record how the connection behaves during everyday operation.
- Reproduce the credible peak. Add the feeds, alarms or playback traffic that could overlap during a real event.
- Keep the traffic running. A short speed burst does not prove sustained CCTV stability.
- Repeat the test when practical. Measurements at different times can expose network congestion that one favourable test misses.
- Test the final router position. A measurement elsewhere on the property may not represent the finished cabinet or equipment location.
- Keep a commissioning record. Save camera settings, measured uplink and observed stream behaviour for later troubleshooting.
6. Use the CCTV calculation to decide what kind of 4G router you need
Once the network load has been proven, router selection becomes more specific. The question is no longer “Which model has the biggest speed number?” It becomes “Which hardware architecture fits this particular site?”
Move from CCTV requirement to router direction
Suitable where the traffic requirement is modest and the local installation does not need a large port layout.
Useful when the router sits close to cameras, an NVR or other equipment in the edge cabinet.
Worth reviewing when the measured workload and the available carrier network genuinely justify more LTE capability.
More relevant when cellular redundancy is part of the project availability requirement.
These are different deployment directions rather than automatic upgrades. A small camera site does not necessarily benefit from more Ethernet ports or dual SIM, while an unattended monitoring site may value redundancy more than a higher theoretical LTE category.
E-Lins 4G router options for different CCTV site requirements
The four products below represent different project directions. Match the product to the measured CCTV workload, local interfaces and redundancy requirement rather than treating them as a simple “good, better, best” ranking.
H685t
A compact industrial 4G direction for smaller CCTV nodes where the camera workload fits a straightforward cellular backhaul design.
H820t-P1
A practical direction when the CCTV cabinet needs PoE Out and a larger local Ethernet layout around cameras, an NVR or other network devices.
H750tt-CAT12
A dual-SIM CAT12 direction for sites where the measured video workload and available mobile network justify a higher LTE category.
H900t-P1
A larger industrial 4G direction when the project needs Gigabit Ethernet, PoE Out and a configuration that can support cellular redundancy requirements.
If none of these four hardware directions matches the installation, continue through the E-Lins IoT 4G Router range rather than forcing the project into a model that does not fit its SIM, interface or network requirements.
Projects where PoE is part of the installation should also review the E-Lins 4G/5G PoE Router range after confirming whether the design needs PoE input, PoE output or a separate PoE switch.
What should be confirmed before ordering?
Frequently asked questions
How much data does one CCTV camera use over 4G?
Does upload speed matter more than download speed for remote CCTV?
How should motion-triggered recording change the monthly data estimate?
Is a CAT12 router automatically better for CCTV?
Should a remote CCTV site use dual SIM?
Size the camera load first, then confirm the router configuration
The most useful request is not “I have eight cameras—what router should I buy?” Send the project information that determines the real network requirement.
Before requesting a recommendation, prepare:
- camera count and transmitted bitrate per stream;
- normal and peak simultaneous streams;
- continuous, event-based or on-demand transmission behaviour;
- estimated monthly cellular-data requirement;
- measured upstream performance at the installation location;
- deployment country and intended mobile carrier;
- SIM redundancy requirement;
- Ethernet, PoE, power and remote-management requirements.
With those values, E-Lins can narrow the available router configurations around the actual CCTV deployment instead of relying on camera count or theoretical LTE speed alone.
