STEPHEN LEO
NPI 1386205367
Driver in Closter, NJ

Active since June 21, 2019
24 WESTMINSTER AVE, CLOSTER, NJ 07624(201) 784-2039 Get Directions Write a Review

NPPES record last updated: June 21, 2019. Verified against the NPPES registry weekly; last sync: August 09, 2026.

About Stephen Leo NPPES

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

STEPHEN LEO (NPI 1386205367) is an individual driver provider in Closter, New Jersey, licensed in New Jersey (L26047220008592) and active in the NPI registry since June 2019.

NPPES Registry Identity

NPI1386205367
Entity TypeIndividualMale
Primary Taxonomy172A00000X
Provider Legal NameSTEPHEN LEO
Location Address24 WESTMINSTER AVECloster, NJ 07624-1217
Mailing Address24 Westminster AveCloster, NJ 07624-1217 · (201) 784-2039
Sole ProprietorYes
Enumeration DateJune 21, 2019
NPI 1386205367 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyDriverOther Service Providers
Taxonomy Code172A00000X
License Licensed in NJ · L26047220008592
Definition
A person employed to operate a motor vehicle as a carrier of persons or property.
24 WESTMINSTER AVE, Closter, NJ 07624

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 Stephen Leo's NPI number?

The NPI number for Stephen Leo is 1386205367. It was assigned to this individual provider in the NPPES registry on June 21, 2019.

Where is Stephen Leo located?

Stephen Leo practices at 24 Westminster Ave, Closter, NJ 07624. The listed phone number is (201) 784-2039.

What is Stephen Leo'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 Stephen Leo was last updated on June 21, 2019. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 7 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.