RMP 95S TO&FROM CT
Carrying RMP 95S TO&FROM CT over CHANNEL
NW LAS VEGAS, Clark, Nevada
Data updated May 2026
FHWA NBI record, refreshed with each annual release.
Bridge Snapshot: RMP 95S TO&FROM CT
The RMP 95S TO&FROM CT bridge in Clark, Nevada carries RMP 95S TO&FROM CT over CHANNEL. It was built in 1999, making it 27 years old today. The structure is built primarily of concrete and spans 2 sections, stretching 7.5 meters (25 feet) end to end. Daily traffic averages 7,050 vehicles, placing it in the moderately-trafficked tier of Nevada bridges. It is owned and maintained by County Highway Agency.
The latest FHWA inspection records show culvert at 7/9. The weakest component sits in good condition. All reported major components score above the Poor range. Its NBI inventory load rating is 90.5 metric tons.
Sourced from the FHWA National Bridge Inventory. See our methodology for refresh cadence and NBI release vintage.
How RMP 95S TO&FROM CT compares
Live comparison across Nevada.
Historical Sufficiency Rating
PlainBridge-computedFHWA discontinued this calculated item; it does not determine current condition, funding eligibility, posting, or closure. How the historical reference is calculated.
Condition Ratings
Full 0–9 scale + sufficiency-rating breakdown: how condition ratings work.
Structural Details
- Year Built
- 1999
- Material
- Concrete
- Number of Spans
- 2
- Structure Length
- 7.5 m (25 ft)
- Owner
- County Highway Agency
- Avg Daily Traffic
- 7,050 vehicles/day
- Structure Number
- B2708
Location
Data Source
FHWA National Bridge Inventory (NBI).
FHWA NBI Program ↗How to read this record
This page shows what the last federal inspection recorded, not whether RMP 95S TO&FROM CT is safe to cross today. Here is how to use it.
- NBI condition ratings reflect the latest record in this annual dataset, not a live status. Current routine inspection intervals are risk-based.
- Learn how the 0–9 condition scale and Good/Fair/Poor categories are defined. How condition ratings work
- Compare RMP 95S TO&FROM CT against other structures in Clark and across Nevada. Nevada bridges
- Noticed visible damage or a safety concern? Report it to the agency that owns the bridge, or call 911 in an emergency. How to report a bridge
Condition codes come straight from the FHWA National Bridge Inventory and are not a real-time safety judgment. Only the owning agency, a state DOT, county, or other owner, can post, restrict, or close a bridge.
Frequently Asked Questions
What do the condition ratings mean for RMP 95S TO&FROM CT?
RMP 95S TO&FROM CT in Clark, Nevada on the FHWA's 0–9 scale.
How often is RMP 95S TO&FROM CT inspected?
RMP 95S TO&FROM CT's responsible agency sets its routine interval under FHWA's risk-based inspection rules; this page does not expose the scheduled interval. It carries about 7,050 vehicles per day.
What does “structurally deficient” mean in older bridge reports?
FHWA retired that reported status beginning with the 2018 archive. RMP 95S TO&FROM CT is currently shown as Good condition from its component ratings; that category is not a live closure or safety decision.
What is the inventory load rating for RMP 95S TO&FROM CT?
RMP 95S TO&FROM CT has an NBI inventory load rating of 90.5 metric tons.
Who is responsible for maintaining RMP 95S TO&FROM CT?
RMP 95S TO&FROM CT is owned and maintained by County Highway Agency.
How old is RMP 95S TO&FROM CT and does age affect safety?
RMP 95S TO&FROM CT was built in 1999, making it 27 years old.
Disclaimer: Bridge condition data is from the FHWA NBI and reflects the last reported inspection. A Poor condition rating is not a live declaration that a bridge is closed or unsafe for travel. For current closure, posting, or safety information, contact the responsible transportation agency.
Every figure on PlainBridge is rendered directly from federal source data, no number is typed in by an editor. This page draws directly on federal source data, no figure is typed in by an editor. See our editorial standards & corrections policy, the methodology behind these numbers, or report a data error.