Numbers starting with 203-664 in Bridgeport, CT
This page collects user-reported phone numbers starting with 203-664, a prefix associated with Bridgeport, CT and listed under CABLEVISION LIGHTPATH.
Reported numbers
2
Reports in last 7 days
0
Reports in last 30 days
0
Last activity
May 9, 2023
Location
Bridgeport, CT
Number type
Landline
What stands out about this prefix
This prefix currently has 2 reported numbers on who-called.us. The latest visible activity for this prefix was recorded on May 9, 2023.
In the deduplicated comment sample, the most frequent label is unknown; other labels include silent call.
The reference data for this prefix points to Bridgeport, CT. In the available metadata, this range is labeled as landline. The listed carrier for this prefix is CABLEVISION LIGHTPATH. Because this prefix belongs to area code 203, it can also be compared with broader reporting patterns across that area code.
How this prefix is being reported
These categories come from classified user reports tied to numbers starting with 203-664. They help show whether reports cluster around one kind of call or are spread across multiple patterns.
Type
Reports
Share
Unknown
3
75%
Silent call
1
25%
Recent comment examples
The comments below are recent examples from reports tied to numbers starting with 203-664. They add real wording and context that category labels alone cannot show.
Recently reported numbers
The list below shows recently active numbers tied to this prefix.
1-203-664-2308
Received a call from this phone number. Answered and they hung up. Normally I don't answer unknown calls.
1-203-664-3409
Has called me a few times. When I answer the call they don't say anything and they hang up after a few seconds. Another time wasting number 203-664-3409
1-203-664-3409
I answered and was disconnected immediately. Normally I wouldn’t answer but I’m expecting a call
1-203-664-3409
Two days ago on the 8/27/2021 this number 2036643409 tried to call me. I answered the phone but there was nobody on the other side. I decided to call it back but we were cut off. I thought it was a problem with connectio…