020 3472 5259
Also shown as:
- 020 3472 5259
- +44 20 3472 5259
AI Summary
Based on 1 community report
This London number, registered to Mi Telecom, has received one report describing a caller claiming you are owed money back from a crypto scam. As this is a common tactic used to lure people into further scams, it's best to be cautious. If you receive this call, do not provide any personal information and hang up.
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 totalThey claimed to be from a company saying I was owed money from a crypto scam
Share Your Experience
Help others by reporting what happened
About 020 3472 5259
What type of number is 020 3472 5259?
The phone number 020 3472 5259 (also written as +44 20 3472 5259) 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 3472 5259 safe to answer?
Based on 1 community report, this number has received mixed reports from our community. The current risk score is 62% .
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 3472 5259
- Country
- 🇬🇧 United Kingdom
- Network
- Mi Telecom
- Area
- London
- Type
- Geographic
- First Seen
- 19 Aug 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