EYONG BATOU
NPI 1811534001
Driver in Houston, TX

Active since December 06, 2019
6403 SIERRA BLANCA DR APT 1705, HOUSTON, TX 77083(347) 397-5294 Get Directions Write a Review

NPPES record last updated: December 6, 2019. Verified against the NPPES registry weekly; last sync: August 16, 2026.

About Eyong Batou NPPES

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

EYONG BATOU (NPI 1811534001) is an individual driver provider in Houston, Texas and active in the NPI registry since December 2019.

NPPES Registry Identity

NPI1811534001
Entity TypeIndividualFemale
Primary Taxonomy172A00000X
Provider Legal NameEYONG BATOU
Location Address6403 SIERRA BLANCA DR APT 1705Houston, TX 77083-1547
Mailing Address6403 Sierra Blanca Dr Apt 1705Houston, TX 77083-1547 · (347) 397-5294
Sole ProprietorYes
Enumeration DateDecember 6, 2019
NPI 1811534001 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.
6403 SIERRA BLANCA DR APT 1705, Houston, TX 77083

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 Eyong Batou's NPI number?

The NPI number for Eyong Batou is 1811534001. It was assigned to this individual provider in the NPPES registry on December 6, 2019.

Where is Eyong Batou located?

Eyong Batou practices at 6403 Sierra Blanca Dr Apt 1705, Houston, TX 77083. The listed phone number is (347) 397-5294.

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