Fleet Route Optimization Telematics

This dataset offers comprehensive telematics records for transportation fleets, including trip-level details on routes, fuel consumption, idle times, emissions, and sensor-detected anomalies. It is ideal for optimizing fleet operations, supporting sustainability initiatives, and enabling advanced AI/ML analytics for smart city logistics and cost reduction.

  • last updated 27 Nov 2025
  • by GoMask
The brief that made it

AI/ML-powered route optimization for fleet efficiency

Sample rows

preview · 8 of 120 rows · all 23 columns
vehicle_idstringcargo_typestringaverage_speed_kphfloatanomaly_detectedbooleanstatestringroute_idstringtrip_idstringdriver_idstringstart_timedatetimeend_timedatetimestart_latitudefloatstart_longitudefloatend_latitudefloatend_longitudefloatdistance_kmfloatfuel_consumed_litersfloatidle_time_minutesfloatmax_speed_kphfloatanomaly_typestringemissions_kg_co2floatcargo_weight_kgfloatcitystringcountrystring
TRK-001furniture28.2falseNYR101T0001D0012024-06-01T07:05:00Z2024-06-01T08:02:00Z40.7128-74.00640.7306-73.935223.14.78.254none10.1300New YorkUSA
TRK-002food18.3trueCAR102T0002D0022024-06-01T10:15:00Z2024-06-01T11:06:00Z34.0522-118.243734.0407-118.246814.22.94.439engine6.8550Los AngelesUSA
TRK-003textiles22.2falseEnglandR103T0003D0032024-06-02T15:52:00Z2024-06-02T16:51:00Z51.5074-0.127851.5155-0.142719.94.26.148none9475LondonUK
TRK-004medical supplies18trueIle-de-FranceR104T0004D0042024-06-03T09:30:00Z2024-06-03T10:28:00Z48.85662.352248.86472.348812.52.53.236fuel_leak5.2620ParisFrance
TRK-005furniture15.8falseBerlinR105T0005D0052024-06-03T14:00:00Z2024-06-03T14:44:00Z52.5213.40552.5413.4110.722.633none4.1285BerlinGermany
TRK-006textiles11.1falseMoscowR106T0006D0062024-06-04T05:41:00Z2024-06-04T06:27:00Z55.755837.617355.7737.628.91.72.729none3.4120MoscowRussia
TRK-007food16.9trueTokyoR107T0007D0072024-06-04T12:45:00Z2024-06-04T13:49:00Z35.6895139.691735.6804139.76915.62.76.734brake5.7330TokyoJapan
TRK-008medical supplies12.4falseShanghaiR108T0008D0082024-06-05T08:23:00Z2024-06-05T09:12:00Z31.2304121.473731.24121.489.82.11.928none4190ShanghaiChina

What the 120 rows show

from the 120-row sample

Electronics (cargo type) stands out: mean average_speed_kph is 12.9, against 18.2 for the rest.

  • 19%anomaly_detected = true
  • 18.1median average_speed_kph
  • 5anomaly types
  • 20countries
  • 32cities
  • 12.8median distance_km
Mean average_speed_kph by cargo_type107 rows
0204018.6pas…39 r…12.9ele…12 r…20.3fur…11 r…19.9food11 r…13.5boo…11 r…19.3med…9 ro…18.3tex…8 ro…15.3sci…6 ro…
average_speed_kph120 rows, in bands of 2.5
015304919232117143827.52032.5average_speed_kph →

Median 18.1, from 8.7 to 31.9.

state120 rows · top 10 of 35 values
  1. Tokyo12
  2. CA11
  3. NY8
  4. Berlin8
  5. Moscow7
  6. England6
  7. Île-de-France6
  8. Lazio5
  9. Lombardy5
  10. Madrid5
23 columns by typefrom the column list below
  • string 9
  • float 11
  • datetime 2
  • boolean 1

Columns

23 columns in four groups
blueprint · 23 columns
columntypedescriptionexample
Text 9 columns
vehicle_idstringUnique identifier for each vehicle in the fleetuniqueTRK-001
route_idstringUnique identifier for the assigned routeR101
trip_idstringUnique identifier for each trip instanceuniqueT0001
driver_idstringUnique identifier for the driver operating the vehicleD001
anomaly_typestringType of anomaly detected (if any), e.g., 'engine', 'brake', 'temperature', 'none'engine · brake · temperature · fuel_leak · none · optionalnone
cargo_typestringType of cargo transported during the trip8 types · optionalfurniture
citystringCity where the trip primarily occurredoptionalNew York
statestringState or region where the trip primarily occurredoptionalNY
countrystringCountry where the trip primarily occurredoptionalUSA
Numbers 11 columns
start_latitudefloatLatitude coordinate where the trip started-90 to 9040.7128
start_longitudefloatLongitude coordinate where the trip started-180 to 180-74.006
end_latitudefloatLatitude coordinate where the trip ended-90 to 9040.7306
end_longitudefloatLongitude coordinate where the trip ended-180 to 180-73.9352
distance_kmfloatTotal distance covered during the trip in kilometers0 or more23.1
fuel_consumed_litersfloatTotal fuel consumed during the trip in liters0 or more4.7
idle_time_minutesfloatTotal time the vehicle spent idling during the trip, in minutes0 or more8.2
average_speed_kphfloatAverage speed of the vehicle during the trip in kilometers per hour0 or more28.2
max_speed_kphfloatMaximum speed reached during the trip in kilometers per hour0 or more54
emissions_kg_co2floatEstimated CO2 emissions for the trip in kilograms0 or more · optional10.1
cargo_weight_kgfloatWeight of cargo transported during the trip in kilograms0 or more · optional300
Dates and times 2 columns
start_timedatetimeTimestamp when the trip started2024-06-01T07:05:00Z
end_timedatetimeTimestamp when the trip ended2024-06-01T08:02:00Z
True or false 1 column
anomaly_detectedbooleanIndicates if any sensor-detected anomaly occurred during the tripfalse

Use it for

  • anomaly detect…19%23 of 120 rowsmean average speed kp…18.6pass…12.9elec…20.3furn…19.9food

    A transportation dashboard

    The anomaly_detected rate, average_speed_kph by cargo_type and a breakdown of state. Excel, Power BI or Tableau.

  • Why do the 12 electronics rows have a mean average_speed_kph of 12.9?

    A root-cause class exercise

    Hand out the rows and one question. The answer is in the data, not in the brief.

  • A software demo

    Believable vehicles with route_id, trip_id and driver_id to fill a screen in front of a buyer.

Not quite right?

Make it yours.

Same 23 columns, your size and your rules. See 20 rows before you pay.

Preview 20 rows free

1,000 rows: $1.99 · 10,000: $12.99One-time. No subscription. All prices

This dataset120 rows23 columns
Yours1,000 rows23 columnscity: UK only

blueprint · fleet-route-optimization-telematics

Behind this dataset

Same schema. As many rows as you need.

These 120 rows came out of a blueprint — 23 columns with generation rules behind each one. Open it in Data Factory to retune a column, add your own, wire in foreign keys, and run it at the size you actually need.

Rules it was built with
  • Each row represents a completed fleet route trip
  • Include GPS trace summary, fuel usage, and idle duration
  • Sensor anomalies logged with timestamp and type
  • Electric and combustion vehicles differentiated
  • Weather impact noted per trip
  • Route efficiency score calculated for each journey
Rows
Open the blueprint in Data Factory

1 credit per row. Preview 20 rows free. Buy rows for the full run.

Exports
CSV, JSON, JSONL, Parquet, SQL, Excel, TSV, XML
Licence
yours to use, including commercially
API slug
fleet-route-optimization-telematics

What should your data show?

Preview 20 rows free
No signup. No card.