01306 321365
Also shown as:
- 01306 321365
- +44 1306 321365
AI Summary
Based on 1 community report
Calls from this Dorking-based number appear to be a nuisance call from an Unknown number with no voicemail left. The single report has zero upvotes and zero downvotes, so confidence is low. The spam score sits at 44/100, suggesting only moderate risk. If you answer and it asks for personal info, hang up and avoid sharing details; consider blocking the number if it repeats.
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 , Number not recognised
Share Your Experience
Help others by reporting what happened
About 01306 321365
What type of number is 01306 321365?
The phone number 01306 321365 (also written as +44 1306 321365) is a UK landline number originating from the Dorking area in England . Calls to this number are charged at standard UK landline rates, usually included in call packages.
Is 01306 321365 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
- 01306 321365
- Country
- 🇬🇧 United Kingdom
- Network
- DIDWW Ireland
- Area
- Dorking
- Type
- Geographic
- First Seen
- 26 May 2026
Protection Guides
Location
Dorking, United Kingdom
This number originates from the Dorking 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