10,412,711Rank in United Kingdom
5,378,018Worldwide Rank
| Monthly pages viewed | 6,804 | |
| Monthly visits | 2,268 | |
| Value per visitor | -- | |
| Estimated worth | £1,072.11 | |
| External links | 189 | |
| Number of pages | 375 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Visitors
| Traffic History 90 Day Average | ||
| Worldwide Rank | 4,519,343 |  1,264,185 |
|---|---|---|
| Daily Visitors | 43 | -51.46% |
| Daily Visitors Rank | 5,045,040 | 2,112,981 |
| Daily Pageviews | 150 | -3.87% |
| Daily Pageviews Rank | 4,207,496 |  -115,840 |
| Pageviews Per User | 3.00 | +100% |
Content
www.Factjapan.com
Age: It went live on August 4th 2005, making it over 12 years, 8 months old.
- Popular pages
- factjapan.com FACT
- factjapan.com FACT
- factjapan.com FACT
- factjapan.com FACT
- factjapan.com FACT
The site has about 47 users daily, viewing on average 3.00 pages each.
Links- Links out
- seetickets.com Buy concert, festival, theatre, sports and event tickets from the
- wegottickets.com WeGotTickets - Your Online Box Office
- sonispherefestivals.co.. Sonisphere Festival, The worlds largest touring festival... In
- myspace.com Greeley Estates | Free Music, Tour Dates, Photos, Videos
| Server Location | |
| Japan Network Information Center Chiba-ken Iso Japan 35.08, 140.1 | |
Its web server is located at Japan Network Information Center (Chiba-ken, Iso.) ns1.avexnet.com, and ns2.sphere.ad.jp are its DNS Nameservers. Factjapan.com's server IP number is 210.136.114.67.
IP: 210.136.114.67
| PING www. (210.136.114.67) 56(84) bytes of data. | |
| 64 bytes from com2.avexnet.com (210.136.114.67): icmp_seq=1 ttl=49 | 145 ms |
| 64 bytes from com2.avexnet.com (210.136.114.67): icmp_seq=2 ttl=49 | 145 ms |
| 64 bytes from com2.avexnet.com (210.136.114.67): icmp_seq=3 ttl=49 | 144 ms |
| --- www. ping statistics --- | |
| 3 packets transmitted, 3 received, 0% packet loss, time 2000ms | |
| rtt min/avg/max/mdev = 144.891/145.066/145.286/0.164 ms | |
| rtt min/avg/max/mdev = 144.891/145.066/145.286/0.164 ms |
Pinging the server, resulted in a 145 ms response.