Aerial view of a multi-level road junction with traffic→ 640/h← 580/hTrucks 9% · Pedestrians 120/h
Traffic & vehicle analytics

Every vehicle counted — by type, direction and hour

RVC.DIGITAL counts the vehicles that pass a site — cars, motorcycles, trucks and buses, by direction and by hour — alongside pedestrians and cyclists. For a roadside billboard, that is its real audience. For a city or a retail park, it is a traffic count without loops or clipboards. No plates read, nothing recorded.

What you get

Roadside audience for your site.

Vehicles heading towards the face, by type and hour — the figure an advertiser can be charged for — plus pedestrians and cyclists from the same camera.

Traffic counts without infrastructure.

Direction and vehicle-mix counts from a camera on a pole or an existing stream — for a week, a season or for good. No cutting the road, no manual counts.

Patterns you can plan on.

Peak hours, weekday and weekend profiles, truck share, inbound/outbound balance — per site, comparable across sites, exportable.

What we measure at a site

Every vehicle is tracked only while it is in view and counted once; no number plate is read, no image is stored. Privacy & compliance →

  • Vehicle count by type — car, motorcycle, truck, bus
  • Direction of travel (towards / away, in / out)
  • Traffic flow over time — hourly and daily profiles
  • Pedestrians and cyclists in the same view
  • Combined roadside audience for an advertising face
  • Any date range, site-to-site comparison
  • CSV export, API, webhook
  • Traffic flow state — free-flowing, slow or congested — on request, typically used to trigger content on roadside screens.
Car
Motorcycle
Truck
Bus
Pedestrian
Cyclist
→ towards the face← away
Vehicle types and directions counted — illustrative

Where it is used

A bright advertising screen on a building beside a busy road at night

Roadside billboards and highway DOOH

The audience that actually drives past the face, by direction. Combine with pedestrian measurement for a complete site figure.

OOH audience measurement →
A city road with cars and a bus, seen from above

Cities and road authorities

Temporary or permanent counting points: direction, vehicle mix, peak profiles, before/after a change.

A car park with rows of parked cars and autumn trees, seen from above

Retail parks, malls, fuel stations, car parks

Inbound and outbound traffic by hour; what share arrives by car, and when.

A city junction at night with lit roads and housing blocks, seen from above

Smart-city and integrator projects

A measurement layer on an existing camera network via RTSP, delivered as a container for your own hardware.

Platform →

How it works

Camera on the site
Measurement area set once
Device boundary
Device boundary
Each vehicle tracked while in view
CarTruckBus
Counts to the dashboard

Built for the roadside

Day and night

Continuous measurement across the full daily cycle.

Its own connection

Own 4G link — no dependency on the site's network.

Existing cameras welcome

RTSP stream; we check the view in the pilot.

Linux, Windows or Android

A device or a container.

Built by a software company, adapted to your site

RVC.DIGITAL is a product, not a project — but it was built by a team that has written enterprise software for 25 years. A vehicle-brand breakdown for a premium site, weather-dependent reach, a count rule written for your junction, a traffic-flow signal that switches a roadside screen's content when traffic slows, a feed into your traffic or sales system — custom metrics and integrations are built into your deployment. Tell us what you need to measure.

Vehicles are counted, never identified

No number-plate reading
On-device processing, no image leaves the device
Pedestrians detected, never recognised
Independent DPIA (November 2024): outside the scope of the GDPR
Read how it works →

Start with a pilot, not a contract

A pilot runs on one to five sites for two to four weeks — a billboard, a junction, a car-park entrance. We agree the camera position and the measurement area with you, install a pre-configured device or connect your existing camera, and close with a report: counts by type, direction and hour. You decide what comes next.

Traffic and vehicle analytics are delivered as individually scoped projects, priced per deployment — the pilot is where we define the scope together.

Frequently asked questions

Does it read number plates?
No — in no configuration. Vehicles are detected, classified and counted while in view; no plate is read, no vehicle is identified, no image is stored.
Can it tell which direction vehicles travel?
Yes. Direction is part of every count, so a billboard's audience includes only vehicles heading towards the face.
Does it work at night and in bad weather?
It measures continuously, day and night. Camera position and lighting matter; we test the site in the pilot.
Can we use our existing traffic or security cameras?
Often yes — an RTSP stream works if the view of the road section is suitable. We check this in the pilot.
How does this compare with loop detectors or manual counts?
A camera device is installed without roadworks, can be moved, and delivers type, direction and pedestrians from the same view. It is a count, not a legal enforcement instrument.
Can it measure the pedestrian audience of the same site?
Yes — same device. See OOH audience measurement →

See your own site counted.