Plumbline / TN / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/tn/contractor/71528-onsite-development-and-rentals · Statuses change; check the live page before you rely on this sheet.

Onsite Development And Rentals, Llc

TN license 71528 (BC - BC Residential, Commercial and Industrial ; A - HRA-A Grading and Drainage ; B1 - HRA-B.1 Base Construction ; B2 - HRA-B.2 Hot Cold Mix ; E2 - Landscaping ; E5 - Miscellaneous Concrete ; AGLM - Aggregate Limit $454,260.00) · ATHENS

License Expired as of 2026-08-25
Source status: "Expired-Grace" 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 71528 (BC - BC Residential, Commercial and Industrial ; A - HRA-A Grading and Drainage ; B1 - HRA-B.1 Base Construction ; B2 - HRA-B.2 Hot Cold Mix ; E2 - Landscaping ; E5 - Miscellaneous Concrete ; AGLM - Aggregate Limit $454,260.00) with status "Expired-Grace", expired 2026-02-28. 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-Grace (in plain terms: inactive)
Expires
2026-02-28
Issued
2017-10-02

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 22333). 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