Plumbline / TN / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/tn/contractor/19876-floyd-storie-roofing-contractors · Statuses change; check the live page before you rely on this sheet.

Floyd Storie Roofing Contractors, Inc.

TN license 19876 (A - A. Asbestos Material Handling/Removing ; AGLM - Aggregate Limit $1,000,000.00 ; BC12 - 12. Roof Decks (BC-12)(incl “gutters & vinyl sid") ; BC20 - 20. Sheet Metal (BC-20) ; BC21 - 21. Roofing – incls gutters & vinyl siding (BC-21)) · ELIZABETHTON

License Expired as of 2026-08-25
Source status: "Expired" per Tennessee Board for Licensing Contractors. The badge summarizes the sourced record below; the record and the issuing agency's live page are what count.

The Tennessee Board for Licensing Contractors snapshot dated 2026-08-25 shows license 19876 (A - A. Asbestos Material Handling/Removing ; AGLM - Aggregate Limit $1,000,000.00 ; BC12 - 12. Roof Decks (BC-12)(incl “gutters & vinyl sid") ; BC20 - 20. Sheet Metal (BC-20) ; BC21 - 21. Roofing – incls gutters & vinyl siding (BC-21)) with status "Expired", expired 2020-01-31. The issuing agency's live page is authoritative for today.

What this status means

The Tennessee Board for Licensing Contractors snapshot from 2026-08-25 does not show this license as active and in good standing. That is what the record said on that date. It is not a judgment about the person or the business. Before you act on it:

Hiring soon? The full checklist: How do I check if a contractor is legit?

What the record shows

Status
Expired (in plain terms: inactive)
Expires
2020-01-31
Issued
1993-01-31

Source: Tennessee Board for Licensing Contractors, snapshot 2026-08-25. The issuing agency's live page is authoritative for today: official TN lookup.

For developers and AI agents: source snapshot file sha256:901b8537970dcb5e314f3a4792a29a1fd3a80a907c21a50ef686d760ee7e748a (row 11329). This is the archived source file we read this record from, and the row within it; the file hash is shared by every record in the same fetch, so it identifies the snapshot, not the individual record.

What we did not check