SCOTT JAMES ABELA LPC
NPI 1700300324
Counselor - Professional in Neptune, NJ

Active since July 26, 2017
402 ROUTE 35, NEPTUNE, NJ 07735(732) 869-2798 Get Directions Write a Review

NPPES record last updated: July 26, 2017. Verified against the NPPES registry weekly; last sync: August 02, 2026.

About Scott James Abela Lpc NPPES

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

SCOTT JAMES ABELA LPC (NPI 1700300324) is an individual professional provider in Neptune, New Jersey, licensed in New Jersey (37PC00593500) and active in the NPI registry since July 2017.

NPPES Registry Identity

NPI1700300324
Entity TypeIndividualMale
Primary Taxonomy101YP2500X
Provider Legal NameSCOTT JAMES ABELACredential: LPC
Location Address402 ROUTE 35Neptune, NJ 07735
Mailing Address73 Truex PlMiddletown, NJ 07748-2333
Sole ProprietorYes
Enumeration DateJuly 26, 2017
NPI 1700300324 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyCounselor · ProfessionalBehavioral Health & Social Service Providers
Taxonomy Code101YP2500X
License Licensed in NJ · 37PC00593500
402 ROUTE 35, Neptune, NJ 07735

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 Scott Abela's NPI number?

The NPI number for Scott Abela is 1700300324. It was assigned to this individual provider in the NPPES registry on July 26, 2017.

Where is Scott Abela located?

Scott Abela practices at 402 Route 35, Neptune, NJ 07735. The listed phone number is (732) 869-2798.

What is Scott Abela's specialty?

The primary specialty registered for this NPI is Counselor, specializing in Professional, with taxonomy code 101YP2500X.

When was this NPI record last updated?

The NPPES record for Scott Abela was last updated on July 26, 2017. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 9 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.