WILLIAM A VENEY
NPI 1811864317
Driver in Lancaster, VA

Active since October 20, 2025
4737 RIVER RD, LANCASTER, VA 22503(804) 925-7297 Get Directions Write a Review

NPPES record last updated: October 20, 2025. Verified against the NPPES registry weekly; last sync: August 16, 2026.

About William A Veney NPPES

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

WILLIAM A VENEY (NPI 1811864317) is an individual driver provider in Lancaster, Virginia and active in the NPI registry since October 2025.

NPPES Registry Identity

NPI1811864317
Entity TypeIndividualMale
Primary Taxonomy172A00000X
Provider Legal NameWILLIAM A VENEY
Location Address4737 RIVER RDLancaster, VA 22503-3322
Mailing Address4737 River RdLancaster, VA 22503-3322 · (804) 925-7297
Sole ProprietorNo
Enumeration DateOctober 20, 2025
NPPES CertifiedOctober 20, 2025
NPI 1811864317 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyDriverOther Service Providers
Taxonomy Code172A00000X
Definition
A person employed to operate a motor vehicle as a carrier of persons or property.
4737 RIVER RD, Lancaster, VA 22503

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 William Veney's NPI number?

The NPI number for William Veney is 1811864317. It was assigned to this individual provider in the NPPES registry on October 20, 2025.

Where is William Veney located?

William Veney practices at 4737 River Rd, Lancaster, VA 22503. The listed phone number is (804) 925-7297.

What is William Veney'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 William Veney was last updated on October 20, 2025. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 9 months 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.