DANIEL TIMOTHY BOND LPC
NPI 1184756926
Counselor - Professional in Florissant, MO
About Daniel Timothy Bond Lpc NPPES
Official registry information on file with the National Plan and Provider Enumeration System.
DANIEL TIMOTHY BOND LPC (NPI 1184756926) is an individual professional provider in Florissant, Missouri, licensed in Missouri (2000175173) and active in the NPI registry since March 2007. He is enrolled in Medicare PECOS, maintains a secondary practice location in Florissant, and is a graduate of Other (1995).
NPPES Registry Identity
Specialties & Licenses
Secondary Practice Location 1
Other Identifiers 1
Medicare Participation & PECOS CMS
Medicare enrollment, assignment, and ordering and referring status from the CMS PECOS system.
Medicare Enrollment Status
Enrolled in Medicare (PECOS)
Daniel Timothy Bond Lpc is registered in the CMS Provider Enrollment, Chain and Ownership System (PECOS).
Other Providers at the Same Location NPPES 6
Providers registered at the same practice address, or within the immediate area, according to the NPPES registry.
FLORISSANT, MO 63033
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 Daniel Bond's NPI number?
The NPI number for Daniel Bond is 1184756926. It was assigned to this individual provider in the NPPES registry on March 9, 2007.
Where is Daniel Bond located?
Daniel Bond practices at 11701 W Florissant Ave, Florissant, MO 63033. The listed phone number is (314) 972-8132.
What is Daniel Bond's specialty?
The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.
Is Daniel Bond enrolled in Medicare?
Yes. Daniel Bond is registered in the Medicare PECOS enrollment system.
When was this NPI record last updated?
The NPPES record for Daniel Bond was last updated on July 29, 2026. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 8 days 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.