020 8834 9178
Also shown as:
- 020 8834 9178
- +44 20 8834 9178
AI Summary
Based on 1 community report
Calls from this London number are currently unverified. One report indicates a missed call with no message left, and no subsequent callbacks. Without more information or community feedback, it's difficult to determine the nature of these calls. It's best to remain cautious and avoid answering if you don't recognise the number.
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 totalGot a call from that number but they didnt leave a message and havent called back
Share Your Experience
Help others by reporting what happened
About 020 8834 9178
What type of number is 020 8834 9178?
The phone number 020 8834 9178 (also written as +44 20 8834 9178) 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 8834 9178 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 8834 9178
- Country
- 🇬🇧 United Kingdom
- Network
- BT
- Area
- London
- Type
- Geographic
- First Seen
- 09 Jul 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