How we count

The crossing numbers on crossbuck.app come from public data from the Federal Railroad Administration (FRA). This page explains where they come from and how we count them, so you can check our work.

Where the numbers come from

• Blocked crossing reports: the FRA's Public Blocked Crossing Incident Reporter (opens in a new tab), where anyone can report a railroad crossing blocked by a stopped train. We use every report from Dec 2019 to Sep 2026, and add new ones nightly. The FRA doesn't verify reports, and neither do we.
• Crossing details: the U.S. Department of Transportation's Crossing Inventory (Form 71) (opens in a new tab): each crossing's location, street, railroad and train counts, as reported by railroads and states. Some details are a few years old.

Both are U.S. government data. Crossbuck isn't affiliated with the FRA, the Department of Transportation or any railroad.

We count reports, not blockages

When several people report the same blockage, each report counts. So the numbers show how often a crossing was reported blocked, not how many separate blockages there were. The FRA's feed also contains rows repeated exactly (same crossing, same minute, same answers), and we count each of those once. Reports that differ in any way, even only in their comments, are kept.

Which crossings are listed

• A crossing gets its own page once it has 10 or more reports.
• An area gets a page once it has 3 or more crossing pages; smaller places are listed by state.
• "Nearby" crossings are those within about a mile (1.5 km) that also have pages.

What each number means

• Reports in the past year: reports from Oct 2025 to Sep 2026.
• How long it lasted: the person reporting picks how long the crossing was blocked from the FRA's choices, from "0–15 minutes" to "More than one day". "More than 30 minutes" is the share of reports that picked 31–60 minutes or longer, and "more than an hour" those that picked 1–2 hours or longer. It's their estimate, not a measurement.
• Most recent report: the date of the latest report, in the crossing's local time.

When a crossing is usually blocked

Train schedules change, so the busiest times use only the last two years of reports (since Sep 2024), counted by the local time at the crossing. We only call a time "most often" when it clearly stands out:

• The busiest stretch of one to four hours needs at least 5 reports, at least one and a half times its share if reports were spread evenly, and a clear lead (20% or more) over the busiest two hours at any other time.
• "Reported at every hour" means there were reports in every hour of the day and no two hours in a row hold a fifth of them.
• A busiest day of the week is named only when one day leads alone with at least 5 reports and 1.3 times the daily average.

When none of these hold, we say the reports don't point to one busiest time.

Live reports in the app

The Crossbuck app also shows whether a crossing may be blocked right now. That comes from drivers using the app who are stopped at the crossing, not from the FRA, and it isn't sent to the FRA. It's never counted in the numbers above.

Spotted a problem?

To report a blocked crossing to the FRA, use its blocked crossing reporter (opens in a new tab). If a number or a crossing's details look wrong here, email support@crossbuck.app. See also our Privacy Policy.