PHILLIP JAMES FRUM JR.
NPI 1366788978
Counselor - Mental Health in Las Vegas, NV

Active since December 31, 2012
3042 BURNHAM AVE, LAS VEGAS, NV 89169(702) 834-2603 Get Directions Write a Review

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

About Phillip James Frum Jr. NPPES

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

PHILLIP JAMES FRUM JR. (NPI 1366788978) is an individual mental health provider in Las Vegas, Nevada and active in the NPI registry since December 2012.

NPPES Registry Identity

NPI1366788978
Entity TypeIndividualMale
Primary Taxonomy101YM0800X
Provider Legal NamePHILLIP JAMES FRUM JR.
Location Address3042 BURNHAM AVELas Vegas, NV 89169-1772
Mailing Address3042 Burnham AveLas Vegas, NV 89169-1772 · (702) 834-2603
Sole ProprietorYes
Enumeration DateDecember 31, 2012
NPI 1366788978 is a valid, active identifier and passes the ISO check-digit test.

Specialties & Licenses

Primary SpecialtyCounselor · Mental HealthBehavioral Health & Social Service Providers
Taxonomy Code101YM0800X
3042 BURNHAM AVE, Las Vegas, NV 89169

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 Phillip Frum's NPI number?

The NPI number for Phillip Frum is 1366788978. It was assigned to this individual provider in the NPPES registry on December 31, 2012.

Where is Phillip Frum located?

Phillip Frum practices at 3042 Burnham Ave, Las Vegas, NV 89169. The listed phone number is (702) 834-2603.

What is Phillip Frum's specialty?

The primary specialty registered for this NPI is Counselor, specializing in Mental Health, with taxonomy code 101YM0800X.

When was this NPI record last updated?

The NPPES record for Phillip Frum was last updated on December 31, 2012. NPI Profile syncs weekly with the NPPES registry data releases published by CMS. This NPI record was last updated 13 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.