Plumbline / ND / contractor

Printed from Plumbline, a free public-record license check. This page: https://contractors.agentlookups.ai/nd/contractor/JOURNEYMAN.831500-kevin-w-muscha · Statuses change; check the live page before you rely on this sheet.

Kevin W Muscha

ND license 831500 (Journeyman Plumber)

License Expired as of 2026-08-25
Source status: "listed in the ND Plumbing Board roster; expired 12/31/2016" per North Dakota State Plumbing Board. The badge summarizes the sourced record below; the record and the issuing agency's live page are what count.
This is Kevin W Muscha's own professional license record, as published by the North Dakota State Plumbing Board. It is not a background check, and it is not a consumer report. Do not use it for any FCRA purpose: not for employment, tenant, credit, or insurance screening. We show only this one occupational-license record and its official source; we do not aggregate other records about this person and we make no characterization of them.

The North Dakota State Plumbing Board snapshot dated 2026-08-25 shows license 831500 (Journeyman Plumber) with status "listed in the ND Plumbing Board roster; expired 12/31/2016", expired 2016-12-31. The issuing agency's live page is authoritative for today.

What this status means

The North Dakota State Plumbing Board 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
listed in the ND Plumbing Board roster; expired 12/31/2016 (in plain terms: inactive)
Expires
2016-12-31
Issued
1978-01-13

Source: North Dakota State Plumbing Board, snapshot 2026-08-25. The issuing agency's live page is authoritative for today: official ND lookup.

For developers and AI agents: source snapshot file sha256:7fe4b6e4b1c329e30b2d9f0e94296f71877e25354a83f7620c43cc2ae1f2b44e (row 4370). 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