Skip to main content
STRIPED DONKEYWe do the heavy lifting.

Lagos · Mobility & logistics

Transport.
Explore journeys, fares and commute records.

Inspect passenger journeys, fares and boarding context, or follow a complete resident commute in the interactive explorer.

Public sample available

Published domain facts

Live Transport Routes
99
Historical range
1940–2026
Certification checks
22
Live Trip Records
24,800,520

Overview

Domain scope

Inspect passenger journeys, fares and boarding context, or follow a complete resident commute in the interactive explorer.

Read the published guide →

Known limits

Generation is complete, but corrected time-of-day occupancy awaits a release refresh. Early decades are reconstructed. National ownership evidence is not a Lagos commercial-fleet benchmark. Visible samples are semantic illustrations, not captured live queries.

Review the source limits →
Full scope reference 2 documented sections
Published domain scope.

Published domain scope.

Follow synthetic journeys, modes and destinations through time. Transport records describe travel; vehicle ownership and government fleet operations remain separate domains.

  • Trace a resident's outward and return journey
  • Compare commute dates, fares and vehicles
  • Inspect the evidence behind transit replays
Live Transport Routes
99
Historical range
1940–2026
Certification checks
22
Live Trip Records
24,800,520
Domain scope.

Domain scope.

Inspect the published scope and deployment boundaries.

Read the published detail

FCTE’s Transport domain represents the city’s commercial mobility ecosystem: transport operators, buses and danfo vehicles, drivers and crews, routes, stops, licenses, fares and individual journeys. Trips form the operational layer, allowing fleet utilization, passenger movement, route activity, travel demand, operating economics and network performance to be studied through time rather than as isolated snapshots.

It does not represent every registered vehicle in the city. Personal and institutional ownership belongs in Vehicles → , while government-owned operational assets belong in Fleet → . Transport instead answers the movement question: how vehicles become services, services become journeys, and journeys connect people to the city.

Because Transport is connected to the wider City Twin™, movement can be analyzed alongside population , employment , businesses , housing , infrastructure and geography — making it possible to study how urban growth and changing demand reshape mobility across Lagos.

Samples & fields

Published sample records.

Free passenger journey sample · rows and field definitions

Free passenger journey sample

Resident nameJourney dateRoute nameBoarding stageAlighting stageVehicle typePassenger fare (local currency)Journey endpoint context
Ibidun Ikenna2022-07-23Ajah-Lekki Town (Danfo)Ajah Motor ParkObalende Motor ParkDanfo40.00OTHER_JOURNEY
Ayoola Aremu2003-08-25Iyana-Ipaja-Oshodi (Danfo)Obalende Motor ParkOjota Motor ParkKeke50.00OTHER_JOURNEY
Ikem Madu2026-03-07Ikorodu-Imota (Danfo)Obalende Motor ParkOjota Motor ParkKeke45.00OTHER_JOURNEY

Showing 3 of 100 sample rows and 8 of 64 fields. “Not recorded” is a display label; downloads retain original values.

Published field definitions · 8 visible fields

Resident name

Supplied name of the synthetic resident; not a real passenger identity.

Original field: SyntheticResident
Example: Ibidun Ikenna

Journey date

Date assigned to this journey by the source.

Original field: JourneyDate
Example: 2022-07-23

Route name

Supplied route name. A named service is not a physical road-segment identifier.

Original field: RouteName
Example: Ajah-Lekki Town (Danfo)

Boarding stage

Name supplied for the passenger’s boarding stage.

Original field: BoardingStage
Example: Ajah Motor Park

Alighting stage

Name supplied for the passenger’s alighting stage.

Original field: AlightingStage
Example: Obalende Motor Park

Vehicle type

Vehicle class supplied for the trip.

Original field: VehicleType
Example: Danfo

Passenger fare (local currency)

Fare for this passenger journey in the city’s local currency. It is distinct from whole-trip revenue.

Original field: FareLocal
Example: 40.00

Journey endpoint context

Source classification comparing journey endpoint wards with available home and work wards. It does not establish trip purpose, a return trip or a transfer.

Original field: JourneyEndpointContext
Example: OTHER_JOURNEY

Complete published field dictionary · 64 fields
SampleIdSample number
Row number assigned in the supplied sample. Original order is retained.Example: 1
DatasetGrainRecord type
One passenger journey per row. Boarding and alighting belong to the same journey.Example: PassengerJourney
ModelAsOfDateModel reference date
Reference date of the supplied model extract, not the date of every journey.Example: 2026-07-02
JourneyIdJourney reference
Identifier for this passenger journey. All 100 journey identifiers are distinct in this file.Example: 469
JourneyGroupIdJourney group reference
Journey grouping identifier supplied by the source. A group does not by itself establish a transfer or return trip.Example: 469
TripIdTrip reference
Identifier for the vehicle trip carrying this passenger. Other passengers may share a trip.Example: 22780207
CitizenIdCitizen reference
Synthetic resident identifier supplied with this journey. Separate free domain samples are not guaranteed to contain the same resident.Example: 20201984
SyntheticResidentResident name
Supplied name of the synthetic resident; not a real passenger identity.Example: Ibidun Ikenna
GenderGender
Resident gender value exactly as supplied.Example: F
DOBDate of birth
Supplied synthetic resident date of birth.Example: 1979-10-10
AgeAtJourneyAge at journey
Resident age at the journey, as supplied.Example: 42
JourneyDateJourney date
Date assigned to this journey by the source.Example: 2022-07-23
BoardedUtcBoarding time (UTC)
Boarding timestamp in UTC, preserving the original precision. No local-time conversion is applied.Example: 2022-07-23 19:28:00.000
AlightedUtcAlighting time (UTC)
Alighting timestamp in UTC, preserving the original precision. No local-time conversion is applied.Example: 2022-07-23 20:21:00.000
JourneyDurationMinutesJourney duration (minutes)
Elapsed minutes for this passenger journey, as supplied.Example: 53
FareLocalPassenger fare (local currency)
Fare for this passenger journey in the city’s local currency. It is distinct from whole-trip revenue.Example: 40.00
PaymentMethodPayment method
Payment method supplied for this passenger journey.Example: Mobile
RouteIdRoute reference
Identifier of the supplied transport route.Example: 54
RouteCodeRoute code
Source route code, preserved as text including leading zeros.Example: 054
RouteNameRoute name
Supplied route name. A named service is not a physical road-segment identifier.Example: Ajah-Lekki Town (Danfo)
RouteTypeRoute type
Route service category supplied by the source.Example: Danfo Route
RouteStatusRoute status (source)
Route status as supplied. This field has no explicit historical effective date; do not infer status at the journey from it.Example: Active
RouteOriginRoute origin
Reference origin of the named route. It may differ from this passenger’s boarding stage.Example: Ajah Motor Park
RouteDestinationRoute destination
Reference destination of the named route. It may differ from this passenger’s alighting stage.Example: Lekki Town
RouteReferenceDistanceKmRoute reference distance (km)
Reference length of the route in kilometres, not measured passenger distance or GPS travel distance.Example: 8.90
DirectionDirection
Source direction label for the journey within its service.Example: Inbound
BoardingStageIdBoarding stage reference
Identifier of the passenger’s boarding stage.Example: 17
BoardingStageCodeBoarding stage code
Source code of the boarding stage, preserved as text.Example: STG-008
BoardingStageBoarding stage
Name supplied for the passenger’s boarding stage.Example: Ajah Motor Park
BoardingStageTypeBoarding stage type
Source category of the boarding stage.Example: Informal Motor Park
BoardingWardIdBoarding ward reference
Ward identifier supplied for the boarding stage.Example: 187
BoardingWardBoarding ward
Ward name supplied for the boarding stage.Example: Sangotedo
AlightingStageIdAlighting stage reference
Identifier of the passenger’s alighting stage.Example: 1
AlightingStageCodeAlighting stage code
Source code of the alighting stage, preserved as text.Example: STG-002
AlightingStageAlighting stage
Name supplied for the passenger’s alighting stage.Example: Obalende Motor Park
AlightingStageTypeAlighting stage type
Source category of the alighting stage.Example: Informal Motor Park
AlightingWardIdAlighting ward reference
Ward identifier supplied for the alighting stage.Example: 86
AlightingWardAlighting ward
Ward name supplied for the alighting stage.Example: Obalende
CrossWardJourneyCrosses ward boundaries
Source flag indicating different boarding and alighting wards.Example: 1
VehicleIdVehicle reference
Identifier of the public transport vehicle used for the trip.Example: 592
VehicleTypeVehicle type
Vehicle class supplied for the trip.Example: Danfo
FuelTypeFuel type
Fuel category supplied for the vehicle.Example: CNG
SeatCapacitySeat capacity
Supplied seating capacity. This is distinct from the trip’s passenger count.Example: 14
YearOfManufactureYear of manufacture
Supplied vehicle manufacture year. No exact manufacture date is inferred.Example: 2009
VehicleStatusVehicle status (source)
Vehicle status as supplied. This field has no explicit historical effective date; a decommissioned vehicle can have earlier journeys.Example: Decommissioned
OperatorIdOperator reference
Operator identifier supplied by the Lagos extract. Separate route and vehicle operator identifiers are not present.Example: 55
DriverCitizenIdDriver citizen reference
Synthetic resident identifier supplied for the driver.Example: 21627462
PassengerCountPassenger count
Passenger count for the whole vehicle trip, not the number of sample rows for this journey.Example: 10
TripRevenueLocalWhole-trip revenue (local currency)
Revenue supplied for the whole vehicle trip. Do not treat it as this passenger’s fare or sum it across repeated trip references.Example: 400.00
HouseholdIdHousehold reference
Household identifier supplied for the resident’s journey-date context. NULL means no household context is supplied.Example: 4312216
HomeWardIdHome ward reference
Home ward identifier supplied for the resident’s journey-date context.Example: 187
HomeWardAtJourneyHome ward at journey
Home ward name supplied for the journey date, where available.Example: Sangotedo
HasAsOfHouseholdContextHousehold context available
Source flag indicating household context is available for the journey date.Example: 1
ContractIdContract reference
Employment contract identifier supplied for the journey-date context, where available.Example: 45001
EmploymentStartDateEmployment start date
Start date of the supplied employment context. This is not the journey date.Example: 2020-12-26
EmploymentEndDateEmployment end date
End date of the supplied employment context. NULL is preserved without inventing an end date.Example: 2011-10-26
EmployerIdEmployer reference
Employer identifier supplied for the journey-date context, where available.Example: 8380
EmployerNameEmployer name
Synthetic employer name supplied for the journey-date context.Example: AGR Enterprises 0003287
WorkWardIdWork ward reference
Work ward identifier supplied for the journey-date context.Example: 245
WorkWardAtJourneyWork ward at journey
Work ward name supplied for the journey date, where available.Example: Lekki-Town
HasAsOfEmploymentContextEmployment context available
Source flag indicating employment context is available for the journey date.Example: 1
JourneyEndpointContextJourney endpoint context
Source classification comparing journey endpoint wards with available home and work wards. It does not establish trip purpose, a return trip or a transfer.Example: OTHER_JOURNEY
RichnessScoreSource richness score
Source-provided richness score retained unchanged. It is not a marketplace quality rating or a statistical sampling weight.Example: 8
SampleHashSource sample hash
Original source sample hash retained as text. Download integrity is recorded separately with a SHA-256 file checksum.Example: 0x00005233C859259B29B633EE0D5BB6B5A4B4F1F73B5413989A2CF0A831098B1C
Download complete field guide JSON ↓
Additional records and schema context 1 documented sections
Records and relationships.

Records and relationships.

Inspect representative records, fields and relationships.

Read the published detail

Showing representative public entity families. View evidence & lineage →

Representative Lagos mobility record shape at the public semantic level. Exact physical fields, row volumes and generation methods are controlled.

EntityRepresentsConnected to
VehicleA commercial/PSV vehicle in an operator's fleetOperator, Route, Trip
PrivateVehicleA household or business-owned vehicleCitizen, Household, Business
DriverLicenseA driver's license, category and renewal historyCitizen, LicenseRenewal
RouteA defined path between an origin and destinationOperator, Stage, Trip
StageA named boarding/alighting point (terminus, exchange, roadside)Route, PassengerJourney
TripA single vehicle journey along a routeVehicle, Route, Crew
PassengerJourneyAn individual passenger's boarding-to-alighting recordCitizen, Trip, Stage
RoutePerformanceAggregated delay/occupancy performance per routeRoute, Employment (via a cross-domain consistency check)
JourneyIdResident IDBoarding StageAlighting StageBoardedFare (₦)Payment
42130871029441Oshodi TerminalCMS Ferry Terminal2026-07-14 07:12250.00Cashless
42130912207765Ikeja AlongBerger BRT2026-07-14 07:18200.00Cash
42131081884402Mile 12 ExchangeOjota BRT2026-07-14 07:31150.00Cash
42131223390117Ketu Roadside MajorObalende Terminal2026-07-14 07:44300.00Cashless

Connections

Known and possible relationships

Review the supported links between domains and their availability.

Domain or contextRelationship and published scope
DemographicsResident and driver identity supplies lifecycle context for mobility records.
Households and EmploymentHome and work context support commute analysis when supplied. They do not establish universal household-to-vehicle or employment-to-trip joins.
GeographyWards and stage locations place routes and journeys in the city.
BusinessOperator-to-business context is documented for commercial transport.
InsuranceAccident claims have a guarded insurance relationship where supported by the city release.
Finance contextFares, fees and fuel spend describe journey economics; they are not asserted as links to bank accounts or government budget records.
Fleet and VehiclesCommercial transport, government fleets and private vehicle ownership are distinct models. Similar vehicle labels are not a cross-domain identity link.
RoadsPlanned relationship only. A named route is not a physical road segment, and the guide reports no road-segment relationship today.
Full relationship reference 1 documented sections
Connected records.

Connected records.

Review the supported links between domains and their availability.

Read the published detail

Connections follow the published domain scope. Optional, contextual and planned relationships retain their stated limits below.

Domain or contextRelationship and published scope
DemographicsResident and driver identity supplies lifecycle context for mobility records.
Households and EmploymentHome and work context support commute analysis when supplied. They do not establish universal household-to-vehicle or employment-to-trip joins.
GeographyWards and stage locations place routes and journeys in the city.
BusinessOperator-to-business context is documented for commercial transport.
InsuranceAccident claims have a guarded insurance relationship where supported by the city release.
Finance contextFares, fees and fuel spend describe journey economics; they are not asserted as links to bank accounts or government budget records.
Fleet and VehiclesCommercial transport, government fleets and private vehicle ownership are distinct models. Similar vehicle labels are not a cross-domain identity link.
RoadsPlanned relationship only. A named route is not a physical road segment, and the guide reports no road-segment relationship today.

Domain guide

Transport · archived guide edition

Striped Donkey V5.89 - 7 September 2026

Counts, prices and “live/today” certification statements reflect this dated edition. They are not a current rerun or offer. The current scope, known limits and accepted quote take priority.

Published scope and limits

Generation is complete, but corrected time-of-day occupancy awaits a release refresh. Early decades are reconstructed. National ownership evidence is not a Lagos commercial-fleet benchmark. Visible samples are semantic illustrations, not captured live queries.

Read the source limits →
Accessible HTML reference 2 documented sections
Modelled entities.

Modelled entities.

Explore the entities and states represented by this domain.

Read the published detail

Individual, business, government, diplomatic, parastatal and NGO ownership — the household side of transport, distinct from commercial fleets. See the dedicated Vehicles → page for ownership, registration and multi-vehicle detail.

Licensing, categories and renewal chronology, age-gated against each citizen's real date of birth.

Routes, stops, operator patterns and scheduled or observed service structures for buses, ferries and other formal shared-mobility services.

Ownership models and route types that reflect how Lagos danfo, bus and other commercial transport operations actually run, not a formalized fiction of them.

Vehicle-level trips and passenger-level journeys, boarding and alighting at named stages.

Crew, maintenance, fares, ticketing, enforcement and accidents — the operational layer behind every trip.

Transport does not claim to reproduce real individuals, vehicles or journeys. Every driver, vehicle, route and trip is synthetic — generated against real regulatory, fleet and demand benchmarks for Lagos, not sampled from any real transport system.

Histories through time.

Histories through time.

Inspect dated lifecycle transitions and historical boundaries.

Read the published detail

Every vehicle, license and journey is dated against the same citizen and household timeline used by every other domain — not generated independently and hoped to line up.

Insured is labeled Planned because AccidentClaim currently holds a guarded relationship into Coverage — the public release records this as a planned cross-domain capability rather than a live relationship. Ownership changes (transfer/resale of a private vehicle) is labeled Planned for the same reason: acquisition and retirement are modeled, a full ownership-transfer chain is not yet.

Evidence & limits

Scope and known limits

Generation is complete, but corrected time-of-day occupancy awaits a release refresh. Early decades are reconstructed. National ownership evidence is not a Lagos commercial-fleet benchmark. Visible samples are semantic illustrations, not captured live queries.

Evidence, findings and release history 2 documented sections
Known limits.

Known limits.

Generation is complete, but corrected time-of-day occupancy awaits a release refresh. Early decades are reconstructed. National ownership evidence is not a Lagos commercial-fleet benchmark. Visible samples are semantic illustrations, not captured live queries.

Read the published detail

Direct route-, trip- and vehicle-registration evidence does not extend back to the 1940s–60s for Lagos. Those early decades are reconstructed rule-by-rule from the historical model, with fares, fees and operating assumptions scaled well below present-day levels. The page therefore treats early-period detail as calibrated history rather than literal observed records.

The strongest ownership-split evidence currently available to this release is the NBS/FRSC Q4 2018 national stock total of 11.8M vehicles (41.2% private, 57.5% commercial, 1.3% government and 0.05% diplomatic). It is useful context, but it is not a Lagos commercial-fleet benchmark and is not presented as one. Private and institutional ownership remains the responsibility of the Vehicles domain.

Peak, midday and off-peak occupancy in the current Lagos trip population still read at roughly the same level. The time-of-day behavior was corrected in the model, but the current Lagos release still reflects the earlier pattern and awaits a release refresh before the improved distribution is visible. The limitation is disclosed here rather than being hidden behind a passing structural check.

Lagos Transport generation is complete for the certified release, while the visible sample remains a representative semantic record rather than a captured live-query result. This affects presentation only, not the generated transport population.

Route, Stage, RoutePerformance and PassengerJourney are fully populated for Lagos: 99 Routes, 20 Stages, 738,000 RoutePerformance rows and 8,850 PassengerJourney rows, verified live on 2026-08-03. All 10 Lagos Transport generation jobs have completed.

View all Transport limitations →

View Full Transport Change Log →

Evidence and assumptions.

Evidence and assumptions.

Review the reference sources and calibration periods.

Read the published detail

Baseline era. No direct vehicle-registration data exists this far back for Lagos — reconstructed rule-based, with fares and fees scaled to a small fraction of present-day levels.

Urban expansion and deregulation.

Safety regulation era.

Managed mass-transit expansion and stronger formal oversight. Lagos BRT was operating at scale, LASTMA enforcement had matured, and the modeled network increasingly separates regulated corridor services from the wider commercial bus and danfo ecosystem.

Contemporary calibration threshold — fare, fee and occupancy scaling reach full modern levels in generation, and Nigeria's real driver/vehicle licensing fee schedule (effective 2020-01-01) anchors present-day cost figures.

Recent hardening and expansion: private-vehicle ownership modeling (2026-07-26), multi-vehicle ownership and a real 99-route Lagos route pool (2026-08-01), and a post-graduation certification hardening pass.

Real published figures — Nigeria NBS/FRSC vehicle evidence and Lagos-specific operator, route and transport-system references.

Computed directly from observed sources, e.g. ownership-split percentages from NBS's national stock totals.

Fleet scale, route activity, operating patterns and mobility behavior are calibrated to cited transport evidence and release-level checks. Exact operating weights and assignment parameters remain controlled.

Individual synthetic assignments are generated under controlled domain rules. Exact sampling, assignment order and parameterization are not published.

View Transport Evidence Catalogue →

Access & datasets

Scope your data request

Choose the records, dates and connected domains you need. Final availability, delivery scope and licensing are agreed with your quote.

Published access and recorded examples 2 documented sections
Explore this domain.

Explore this domain.

Available as Standalone Domain · Multi-Domain Bundle · Full City Twin™

Recorded example.

Recorded example.

Published release reference · These recorded checks are not a current rerun.

Explore the supplied synthetic example and its source references.

Read the published detail

Citizen 15407729, Lagos. Two published synthetic PassengerJourney rows, both starting from Berger Motor Park, three hours apart.

₦35.00, paid by Cash.

₦35.00, paid by Cash — a second real journey the same day, same starting point, different destination.

Explore This Record →