NFA Watch

The ATF does not publish queue information or estimated timelines for NFA applications. Filers are left waiting — sometimes for months — with no meaningful signal about where their application stands or whether the queue is moving.

NFA Watch was built to fill that gap. Community members submit their own approval data — form type, filing date, approval date, owner type, state, and filing method. That data is aggregated, normalized, and surfaced as cohort trends, approval distributions, and queue intelligence.

Sources. The dataset is built from two sources: manual submissions from community members and historical batch imports from publicly shared community records.

Normalization. All entries are standardized before storage. Form types, states, owner types, and filing methods are mapped to canonical values. This prevents minor variations (e.g. "E-File" vs "efile") from creating duplicate data points.

Deduplication. Before each new submission is accepted, it is compared against recent entries with identical key fields. Near-duplicate submissions within a short time window are rejected to protect data quality.

Why medians, not averages. Averages are distorted by outliers. A single 400-day approval would inflate a cohort's average far above what most filers experienced. Medians represent the midpoint of actual reported wait times — a more realistic picture of typical outcomes.

Confidence thresholds. Statistical distributions (typical range, median) are only shown when a cohort has sufficient sample size. Small cohorts are flagged accordingly and excluded from aggregate calculations.

The Operational Frontier is not the oldest individual approval on record. It is the oldest filing cohort — grouped by pending date month — with sustained recent activity: multiple reported approvals in the last 30 days that represent a meaningful share of current queue movement.

A single isolated approval from a very old cohort does not move the frontier. If only 5 approvals have been reported from January while 135 came from April, January does not represent where the queue is actually operating — April does.

Median. The midpoint of reported wait times. Half of approvals in the group were faster; half were slower. This is the primary metric on NFA Watch because it is robust to outliers.

Typical range (P25–P75). The range from the 25th to 75th percentile of reported wait times. This covers the middle 50% of the distribution — if the range is 5–28 days, most approvals in that group fell within that window.

Active cohorts. The number of distinct filing months with at least one reported approval in the last 30 days. Higher numbers suggest the queue is processing multiple cohorts simultaneously.

E-file vs. paper. ATF eForms and paper submissions follow different processing workflows. Wait times can differ materially between methods. When sufficient data exists, NFA Watch surfaces these distributions separately.

• –NFA Watch is unofficial and unaffiliated with the ATF or U.S. government.
• –All data is self-reported and may be incomplete, inaccurate, or biased by who chooses to report.
• –The dataset does not represent all approvals — only those submitted here.
• –Nothing on this site constitutes a prediction of your wait time.
• –Nothing here is legal advice. Consult a qualified attorney for legal questions.
• –Small cohorts with few reports may not reflect true processing patterns.

NFA Watch does not collect or store personal information. Submissions are anonymous — no account or identity is required or retained.

ATF control numbers, if provided, are partially masked before storage. Only the numeric prefix is retained for cohort correlation analysis. The last three digits are never stored.

No user accounts, tracking pixels, advertising networks, or third-party analytics services are used.

The NFA process is opaque by design. Filers wait — often for months — with no meaningful feedback from the ATF about where their application stands or whether the queue is moving at all.

Community forums help, but the information is scattered across threads, anecdotal, and difficult to interpret in aggregate. A single data point about someone's approval doesn’t tell you much. Hundreds of data points, organized by filing cohort and form type, start to reveal patterns.

NFA Watch was built to aggregate that scattered signal into something more useful: cohort trends, operational frontiers, and real distribution data — continuously updated as the community reports.