JUSTIN WESLEY BOYD
NPI 1508600016
Driver in Raleigh, NC

Active since June 20, 2024
11602 JAYMAN DR, RALEIGH, NC 27617(919) 737-3351 Get Directions Write a Review

NPPES record last updated: June 20, 2024. Verified against the NPPES registry weekly; last sync: July 26, 2026.

About Justin Wesley Boyd NPPES

Official registry information on file with the National Plan and Provider Enumeration System.

JUSTIN WESLEY BOYD (NPI 1508600016) is an individual driver provider in Raleigh, North Carolina, licensed in North Carolina (23892604) and active in the NPI registry since June 2024.

NPPES Registry Identity

NPI1508600016
Entity TypeIndividualMale
Primary Taxonomy172A00000X
Provider Legal NameJUSTIN WESLEY BOYD
Location Address11602 JAYMAN DRRaleigh, NC 27617-4222
Mailing Address11602 Jayman DrRaleigh, NC 27617-4222 · (919) 737-3351
Sole ProprietorNo
Enumeration DateJune 20, 2024
NPPES CertifiedJune 20, 2024
NPI 1508600016 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyDriverOther Service Providers
Taxonomy Code172A00000X
License Licensed in NC · 23892604
Definition
A person employed to operate a motor vehicle as a carrier of persons or property.
11602 JAYMAN DR, Raleigh, NC 27617

Frequently Asked Questions NPPES & CMS

Common questions about this NPI record, answered from the official NPPES registry and CMS datasets shown on this page.

What is Justin Boyd's NPI number?

The NPI number for Justin Boyd is 1508600016. It was assigned to this individual provider in the NPPES registry on June 20, 2024.

Where is Justin Boyd located?

Justin Boyd practices at 11602 Jayman Dr, Raleigh, NC 27617. The listed phone number is (919) 737-3351.

What is Justin Boyd's specialty?

The primary specialty registered for this NPI is Driver with taxonomy code 172A00000X.

When was this NPI record last updated?

The NPPES record for Justin Boyd was last updated on June 20, 2024. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 2 years ago. If this record has changed at CMS more recently, you can request an on-demand re-check against the live CMS registry, directly from this page.