Ashleysadventure.co.uk
Ashleysadventure is ranked 826,066 in the United Kingdom. 'Ashley's Adventure | Follow me and my world adventure.'
826,066Rank in United Kingdom
3,938,963Worldwide Rank
Monthly pages viewed | 4,536 | |
Monthly visits | 4,536 | |
Value per visitor | -- | |
Estimated worth | £1,835.09 | |
External links | 13 | |
Number of pages | 30 |
Last Updated: 06/04/2018 . Estimated data, read disclaimer.
Visitors
Traffic History 90 Day Average | ||
Worldwide Rank | 3,310,053 | 1,750,657 |
---|---|---|
Daily Visitors | 86 | -59.77% |
Daily Visitors Rank | 2,732,066 | 1,369,245 |
Daily Pageviews | 0 | -70.90% |
Daily Pageviews Rank | 4,920,911 | 2,672,247 |
Pageviews Per User | 1.10 | -27.92% |
Content
www.Ashleysadventure.co.uk
The site has about 94 users daily, viewing on average 1.10 pages each.
Links- Links out
- dotnetblogengine.net BlogEngine.NET | An open source ASP.NET 4.0 powered blogging engine
- jankoatwarpspeed.com Janko At Warp Speed | I design software that speak human and love
- loopbyte.com Web Hosting India, Dedicated Server, Vps, Web Hosting Company
- highlandholidaycottage.. Self Catering Accommodation in Aviemore, Cairngorms, Highlands and
Server Location | |
Hetzner Online Ag Bayern Gunzenhausen Germany 49.1, 10.75 |
Ashleysadventure.co.uk's server IP number is 46.4.14.136. ns68.1and1.co.uk, and ns67.1and1.co.uk are its DNS Nameservers. Its web server is located at Hetzner Online Ag (Bayern, Gunzenhausen.)
IP: 46.4.14.136
PING www. (46.4.14.136) 56(84) bytes of data. | |
64 bytes from static.136.14.4.46.clients.your-server.de (46.4.14.136): icmp_seq=1 ttl=115 | 120 ms |
64 bytes from static.136.14.4.46.clients.your-server.de (46.4.14.136): icmp_seq=2 ttl=115 | 120 ms |
64 bytes from static.136.14.4.46.clients.your-server.de (46.4.14.136): icmp_seq=3 ttl=115 | 120 ms |
--- www. ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 1999ms | |
rtt min/avg/max/mdev = 120.047/120.408/120.696/0.391 ms | |
rtt min/avg/max/mdev = 120.047/120.408/120.696/0.391 ms |
Pinging the server, resulted in a 120 ms response.