![](http://www.img-urlm.com/i/eyjar.is.jpg)
Eyjar.is
Eyjar is ranked 2,835,306 in the United Kingdom. 'Welcome to Vestmannaeyjar.'
2,835,306Rank in United Kingdom
8,632,812Worldwide Rank
Monthly pages viewed | 2,370 | |
Monthly visits | 1,247 | |
Value per visitor | -- | |
Estimated worth | £792.78 | |
External links | 298 | |
Number of pages | 4,875 |
Last Updated: 06/04/2018 . Estimated data, read disclaimer.
Visitors
Traffic History 90 Day Average | ||
Worldwide Rank | 7,254,464 | ![]() |
---|---|---|
Daily Visitors | 24 | ![]() |
Daily Visitors Rank | 7,356,702 | ![]() |
Daily Pageviews | 0 | ![]() |
Daily Pageviews Rank | 7,700,367 | ![]() |
Pageviews Per User | 1.90 | ![]() |
Content
www.Eyjar.is
- Popular pages
- eyjar.is Welcome to Vestmannaeyjar
- tourist.eyjar.is Eyjamyndir website
- eyjar.is Volcanic eruption in Vestmannaeyjar 1973
- eyjar.is Vestmannaeyjar ,Westman Island
- viska.eyjar.is Welcome to the Frontpage
On average 1.90 pages are viewed each, by the estimated 26 daily visitors.
Links- Links out
- axis.com Axis Communications - Leader in network cameras and other IP
- unep.org United Nations Environment Programme (UNEP) - Home page
- community.joomla.org Joomla! Community Portal
- officelive.com Share Documents and Files Online | Microsoft Office Live
Server Location | |
Tolvun Inc. Vestmannaeyjar Vestmannaeyjar Iceland 63.37, -20.21 |
Its web server is located at Tolvun Inc. Vestmannaeyjar Vestmannaeyjar. There are 4 DNS records, such as ns1.eyjar.is, ns2.eyjar.is, and ns3.eyjar.is. Eyjar.is's server IP number is 85.116.64.5.
IP: 85.116.64.5
PING vey. (85.116.64.5) 56(84) bytes of data. | |
64 bytes from vey. (85.116.64.5): icmp_seq=1 ttl=44 | 172 ms |
64 bytes from vey. (85.116.64.5): icmp_seq=2 ttl=44 | 171 ms |
64 bytes from vey. (85.116.64.5): icmp_seq=3 ttl=44 | 171 ms |
--- vey. ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 1999ms | |
rtt min/avg/max/mdev = 171.497/171.854/172.328/0.592 ms | |
rtt min/avg/max/mdev = 171.497/171.854/172.328/0.592 ms |
Pinging the server, resulted in a 172 ms response.