Dr. Timothy P. Culbert, MD

Dr. Timothy P. Culbert, MD http://cdn.hgimg.com/img/silhouettes/silhouette-male_w120h160_v1.jpg Visit Healthgrades for information on Dr. Timothy P. Culbert, MD. Find Phone & Address information, medical practice history, affiliated hospitals and more.

Specializes in Developmental-Behavioral Pediatrics • Male • Age 55

347 Smith Ave N Suite 300
Saint Paul, MN 55102
OverviewExperienceHospital QualityPatient SatisfactionAppointments & Offices

Key things you need to know about
Dr. Culbert:


Dr. Culbert's Experience

Research training, expertise and qualifications


Patient Satisfaction

Patients' feedback on their experience with Dr. Culbert


8 Facts About Patient Satisfaction Surveys

Patient satisfaction surveys provide a standardized way of reporting about healthcare experiences. But there can be more than meets the eye when reviewing scores. Here's what you should know


Appointments & Offices

Check insurance plans, locations and make an appointment

Accepting new patients?

  • Yes
Children's Specialty Clinics
Childrens Specialty Clinics
2525 Chicago Ave Suite 4150
Minneapolis, MN 55404
Children's Specialty Clinics
Children's Specialty Clinics
347 Smith Ave N Suite 300
Saint Paul, MN 55102
MoreSchedule an appointment

7 Tips to Prepare for Your Appointment

The key to a successful appointment is communication. To get the most out of your visit, prepare ahead of time so you can lead the conversation with your doctor. These 7 tips will get you ready

Find the Right Doctor For You.

Dr. Andrew J. Barnes, MD
1.79 miles away
Dr. James R. Moore, MD
Same location as Dr. Culbert
Dr. Katherine E. Murray, MD
1.37 miles away
Dr. Michael I. Reiff, MD
2 miles away
Dr. Carolyn A. Kippes, MD
10.17 miles away
Dr. William B. Donald, MD
1.28 miles away
Dr. Michele D. Strachan, MD
1.87 miles away
Dr. Jennifer L. Lessin, MD
11.17 miles away
Dr. Laurel M. Wills, MD
8.13 miles away
Dr. Anna M. Kostanecka, MD
11.17 miles away

Find Developmental-Behavioral Pediatric Specialists Near Minneapolis, MN

The VideoCalloutContainer had no content.