A commercial vehicle depot yard before sunrise, panel vans and flatbed trucks parked in bays on wet tarmac behind a chain link fence.

Asset & fleet tracking software

Know where your assets are, and what they did.

TRAKCORP builds asset and fleet tracking software for UK operators. Vehicles, trailers, plant and tools on one live map, with the movement history to back up every job.

Join the pilot programme Talk to the founder

Platform in build
Incorporated 1 February 2026
England and Wales, company 17005499
Great Yarmouth, Norfolk

What the platform does

One live map

Every tracked vehicle, trailer and item of plant renders on a single map, whichever unit it is reporting through. No separate portal per hardware supplier.

Journey history

Positions are kept, not just displayed. A disputed delivery or a challenged site attendance gets answered from the record rather than from memory.

Geofence events

Draw a boundary around a depot, a site or a customer premises. Arrivals and departures are logged as events and can be pushed to your own systems.

An API, not a silo

Most operators already run a job management system. Positions, journeys and geofence events are exposed over a documented REST API so the data reaches it.

How it works

Three moving parts, and none of them are mysterious.

Tracking is not a difficult idea. It is a hardware decision, a data pipeline and a question somebody needs answering three weeks later. Here is how we are building each one.

Fit the hardware, or keep the hardware you have

The platform ingests positions from standard telematics units rather than from a proprietary box you can only buy from us. That covers OBD-II plug-in trackers for vans and cars, hardwired 12V and 24V units for trucks and plant, and battery powered asset tags for trailers, generators, tool chests and anything without a supply to draw from.

If a unit already sits in your vehicles and it speaks a protocol we support, it stays where it is.

An engineer's gloved hands routing a small black telematics unit and its wiring loom into the under dash cavity of a commercial van.

Positions land, and they are kept

Units report on an interval. Each report becomes a stored record with a timestamp, a coordinate pair, speed, heading and the ignition state, and those records are stitched into journeys with a start, an end and a route between them.

Everything below is a design target for first release, published so you can hold us to it.

Moving report interval: Configurable. Target default 60 seconds.
Stationary heartbeat: Configurable. Target default 1 hour.
Event triggers: Ignition on, ignition off, geofence entry, geofence exit, external power loss.
Stored per position: UTC timestamp, latitude, longitude, speed, heading, satellite count, HDOP, ignition state, external voltage.

The record answers the argument

A hire desk wants to know whether the roller went back on Tuesday. A client says nobody attended site. A subcontractor invoices for a run that did not happen. These are the moments a tracking system either earns its cost or does not.

Journey history, geofence arrival and departure logs and utilisation views exist for exactly that: to turn a disagreement into a lookup. Idle plant surfaces in the same view, which is usually cheaper than re-hiring a machine that is sitting in a yard forty miles away.

A muddy construction site compound with a tracked excavator, a small dumper and stacked steel road plates behind temporary fencing.

Platform detail

The specifics, published early on purpose.

We have no customer count to show you and we are not going to invent one. What we can do is state exactly what the platform is being built to do, so that when it ships you can check it against this page.

Anything not yet fixed is marked as unconfirmed rather than quietly omitted.

Hardware classes supported

OBD-II plug-in units. Hardwired 12V and 24V units. Battery powered BLE asset tags reported through a gateway unit.

Protocols being built against

Teltonika Codec 8 and Codec 8 Extended over TCP and UDP. Queclink @Track ASCII. JT/T 808. [TO CONFIRM: the final protocol list at first release, which will be published on this page before the pilot opens]

Position reporting interval

Per asset, per profile. Target default 60 seconds moving, 1 hour stationary. Faster intervals raise data volume and, on battery tags, shorten service life.

Positional accuracy

A property of the GNSS receiver and the sky above it, not of our software. We will publish the manufacturer stated figure per supported unit rather than quote a single number. [TO CONFIRM: per unit accuracy table, pending bench testing of each supported device]

Where data is stored

A United Kingdom region, with no routine transfer outside the UK for position data. [TO CONFIRM: hosting provider and named UK region, to be stated here once the production agreement is signed]

Position history retention

Target default 24 months, configurable down to 3 months per account. Retention is a customer setting because a plant hire business and a courier subcontractor do not have the same evidential need.

Driver privacy

Vehicle tracking records personal data about identifiable drivers, so it sits under the UK GDPR. The platform is being built with a private mode for out of hours use and with account level controls over who can see historic journeys. Our full position is set out in the privacy notice.

Access routes

A responsive web application, plus a documented REST API over HTTPS returning JSON, with token authentication and webhooks for geofence and ignition events.

Mobile applications

Planned for iOS and Android. Nothing is published on the App Store or Google Play today, and the store listings do not exist yet. When they do, the permission table in the privacy notice governs what they ask for.

Pricing structure

Per tracked asset per month. No per user charge, because operations managers, hire desks and finance all need to look at the same map. [TO CONFIRM: the per asset monthly price, to be published here before the pilot programme opens to general sign-up]

Certification status

We do not hold ISO 27001 certification, a SOC 2 report or Cyber Essentials certification, and will not represent otherwise. If that changes, the certificate reference will be published on this page.

Who this is built for

Mid-sized UK operators running paper, spreadsheets and whatever came with the vans.

That is a description of a market condition, not a claim about who our customers are. These are the operations the platform is being designed around.

Mini excavators, telehandlers and compaction rollers lined up on hardstanding in a plant hire yard under a grey sky.

Construction and plant hire Where the machine is, whether it went back, and how many hours it actually ran.

Three white service vans with roof ladder racks parked kerbside on a British suburban street at dusk.

Field service Arrival and departure times per appointment, taken from the geofence rather than from a text message.

Refuse collection vehicles parked in a line beside roll on roll off skips at a municipal waste depot in early morning light.

Waste and recycling Round completion evidence, and containers that stop disappearing between sites.

Curtain sided articulated trailers backed onto loading bay docks at a distribution warehouse on a wet concrete apron.

Logistics subcontractors Trailer location as a first class object, separate from the tractor unit pulling it, so a drop and swap does not lose the asset.

A small excavator beside an open trench on a British street, surrounded by red and white barriers, cones and a compressor trailer.

Utilities Crew and equipment position against a works programme, with a record that survives an audit.

Where we are

The honest version of our stage.

TRAKCORP LTD was incorporated in England and Wales on 1 February 2026. We are building the platform now and working with a small number of pilot operators. We would rather tell you that than pretend to a customer list we have not earned yet.

Every competitor in this category leads with a number: units shipped, vehicles tracked, years in business, data points per day. Those numbers are the whole credibility layer, and we do not have any of them. Inventing them would be the fastest way to become the kind of supplier we would not buy from.

So the site substitutes detail for scale. The hardware classes, the protocols, the reporting intervals, the fields stored per position, the retention default, the hosting region, the pricing shape and the certifications we do not hold are all published above. Every one of those is checkable, and every one of them can be held against us later.

If a claim on this site cannot be verified against Companies House, against the platform itself, or against a document we have published, it is not on this site.

Pilot operators, early enough to change the product.

We want fleet size, asset types and whatever you run today, because at this stage that is genuinely what shapes the build. Email reaches the founder directly.

Join the pilot programme