CSA
SearchMapNewCarriersInsightsCalculator
DataQsBeta2
Guides7
Driver CoachingAPI
LoginRegisterTry FleetTrained
UnknownUSDOT 3537676· CARRIER· EIN 46-3554585
⬇ PDF report

BUILTECH CONSTRUCTION LLC

23 PHEASANT RD, DOYLESTOWN, PA, 18901(215) 345-4710builtechconstruction@yahoo.comJOSEPH FOX
Vetting snapshot
Authority
Unknown
per SAFER
Insurance
No active filing
not required
Vehicle OOS
—
no inspections
Driver OOS
—
no inspections
Crashes 24mo
0
clean
Red flags
1 flag
see details below
80
/ 100

Risk factors

Low riskVioCodes score
Possible reincarnation pattern — tied to an older inactive carrier

A weighted read of the public FMCSA signals below — authority, insurance, out-of-service, crashes, roadside OOS rates, and carrier connections. A starting point for vetting, not a guarantee.

Roadside inspection performance

Out-of-service rate vs national average. Lower is better.

Vehicle0 inspections · 0% OOS · National 22%
Driver0 inspections · 0% OOS · National 6.7%

CSA performance breakdown

FMCSA · August 28, 2026

0 inspections · 0 violations (0 OOS) · —% of inspections had an OOS finding.

0
Inspections
0
Violations
0
OOS violations
0
Distinct codes

Latest FMCSA SMS snapshot. Codes link to the lookup — severity weighting, contest angles, and the DataQs Drafter for each. Click a BASIC to filter the codes.

Company profile

FMCSA census

PRIVATE PROPERTY

Power units
1
on file (MCS-150)
Drivers
3
0 hold a CDL
Annual mileage
0M mi
reported 2022
Recordable crash rate
0.00
per million miles
How far they run · drivers by operating lane
  • Interstate · <100 mi3 drivers
Company officer
JOSEPH FOX
Operation
Interstate
Registered since
2020-12-17
Last MCS-150 update
2023-06-12
Census status
I

Fleet: 1 trucks.

Source: FMCSA Company Census File (data.transportation.gov). Fleet and driver counts are self-reported on the carrier’s most recent MCS-150 filing.

Connections

carrier graph

This carrier shares addresses or officers with 5 other carriers — review the connections below as part of your vetting.

5
Connected carriers
0
Fleet-transfer links
0
Most shared VINs
4
Strong links
Possible reincarnation pattern: JOSEPH R FOX (USDOT 1839402, registered 2008) is inactive, shares this carrier’s address, and predates it — worth checking whether this carrier re-registered to shed a prior record.
Strong· 4
1
ABEL TRANSPORT INC
USDOT 3712186Inactive· CEDAR RAPIDS, IA
Strong
Officer
2
F&M FREIGHT BROKERS INC
USDOT 3426755Active· SOUTHFIELD, MI
Strong
Officer
3
R & J RECOVERY
USDOT 2092228Active· PHOENIX, AZ
Strong
Officer
4
SIR LINES A LOT LLC
USDOT 1992657Active· EDINA, MN
Strong
Officer
Medium· 1
JOSEPH R FOX
USDOT 1839402Inactive· DOYLESTOWN, PA
Medium
Address

Shared VINs come from FMCSA roadside-inspection records — a vehicle inspected under more than one carrier, often a fleet transfer or trailer interchange. Other links come from the FMCSA census. Shared identifiers are common and often legitimate — treat these as leads to investigate, not proof of wrongdoing.

Activity history

5 events
  1. 06/06/2024Federal out-of-service order

    New Entrant Revoked - Failure of Safety Audit

  2. 03/05/2024Federal out-of-service order

    New Entrant Revoked - Refusal of Audit/No Contact

  3. 03/05/2024Out-of-service order rescinded
  4. 06/12/2023MCS-150 update filed

    0.0M mi reported (2022)

  5. 12/17/2020Registered with FMCSA

    PRIVATE PROPERTY

Merged from FMCSA authority, insurance, out-of-service, and census records.

🚛

Operations

Classification

  • PRIVATE PROPERTY

Area served

  • Interstate
★

FMCSA safety rating

Rating
Not rated
Type
—
Rated
—
Last review
—
📄

MCS-150 registration

Form date
2023-06-12
Reported mileage
32,000 mi (2022)
⚡

Got a violation you want to contest?

Use the free AI-powered DataQs Drafter to generate a polished challenge letter — quotes the relevant 49 CFR, predicts your grant chance.

Open the Drafter →
ⓘ
Data sourced from public FMCSA records via safer.fmcsa.dot.gov · Latest FMCSA update: Sep 2026 · Page refreshed: Sep 24, 2026, 5:49 AM. VioCodes is not affiliated with FMCSA. To dispute incorrect data, file a DataQs Request for Data Review.