Register my name | Post with my account

Who Called Us

The phone is ringing, and I don't recognize the number,
All Caller ID says is, "NAME UNAVAILABLE".
Please help me figure out who is calling and what they want

Salt Lake City, UT
16 calls reported from this number.
Who CalledCaller IDDate
unknownBlocked call2013-12-04
TelemarketerProvo UT2013-10-28
ScamBagsPrivate Caller2013-12-16
Don't knowPrivate caller2013-12-04
???Provo UT2013-11-14
PROVO UT2013-11-22
private caller2013-11-22
Provo, UT2013-11-11
Provo UT2013-10-28
Provo UT2013-11-01
Provo UT2013-10-03

Report a phone call from 801-805-0274

Comment on calls from 801-805-0274


December 17th, 2013 Ken TN

Car warranty scam

November 21st, 2013 Illinois IL

We are on the DO NOT CALL list! PLEASE STOP calling!
Caller ID: Unknown

November 16th, 2013 bob NC

called i answered they said hello and they hung up

November 1st, 2013 Karen CA

She said her name was "Jill" calling about my car warranty having expired. I hung up because I have received 4 of these calls this week--not all from the same number. These calls are coming in at my work number and very annoying.

October 28th, 2013 Ronin LA

801-805-0274 - A monkey with a script just called our business line. The spiel : Hi! Did you know that your vehicle warranty has expired? Well it has. Would you like to know how you can obtain a new vehicle warranty at... blah blah blah. How in the heck would this person know that my vehicle's warranty has expired when they didn't ask to speak to anyone in particular, nor did they ever state which vehicle is supposedly expired. Morons. Told them to please say hello to Mr Click. Their response : Mr Click? CLICK! Hung up. Reporting to call to the website. Shows up as Provo UT on Caller ID.

October 28th, 2013 Ronin LA

801-805-0274 - A monkey with a script just called our business line. The spiel :

October 14th, 2013 Flyboy Hong Kong

7th number calling me since the government shutdown. 7th number that my Nokia Lumia has now been assigned to block. Government shutdown affecting the DoNotCall registry, I suspect.