020 8621 1146
Also shown as:
- 020 8621 1146
- +44 20 8621 1146
AI Summary
Based on 1 community report
Calls from this London number are often very brief, with no voicemail left and not ringing long enough to answer. With only one report and no upvotes or downvotes, there's not enough information to determine if this is a scam or a genuine caller. It's best to remain cautious and consider blocking the number if you receive further calls.
1 verified report
Cumulative spam score based on all reports up to each month. Higher percentage means higher reported scam risk. Cumulative spam score based on all reports up to each week. Higher percentage means higher reported scam risk. Cumulative spam score based on all reports up to each day. Higher percentage means higher reported scam risk.
Most helpful reports
1 totalNo voicemail left . Didn’t ring long enough for me to asnwer.
Share Your Experience
Help others by reporting what happened
About 020 8621 1146
What type of number is 020 8621 1146?
The phone number 020 8621 1146 (also written as +44 20 8621 1146) is a UK landline number originating from the London area in Greater London . Calls to this number are charged at standard UK landline rates, usually included in call packages.
Is 020 8621 1146 safe to answer?
Based on 1 community report, this number has received mixed reports from our community. The current risk score is 44% .
Be cautious when answering calls from this number. Verify the caller's identity before sharing any information.
More on nuisance calls
Safety Score
Details
- Tel Number
- 020 8621 1146
- Country
- 🇬🇧 United Kingdom
- Network
- Virgin Media
- Area
- London
- Type
- Geographic
- First Seen
- 30 Jun 2026
Protection Guides
Location
London, United Kingdom
This number originates from the London area code region. The map shows the general geographic area, not an exact location.
Call Types
Breakdown of reported call reasons. Larger segments and bars represent a bigger share of reports.
Is this your number?
Claim ownership to manage reports
We'll verify ownership via callback or documentation