Luckycraft.co.jp
Luckycraft is ranked 14,583,018 in the United Kingdom. 'NETWORK MEMBER'S - LUCKYCRAFT.'
14,583,018Rank in United Kingdom
1,791,663Worldwide Rank
| Monthly pages viewed | 31,752 | |
| Monthly visits | 15,876 | |
| Value per visitor | -- | |
| Estimated worth | £5,649.89 | |
| External links | 422 | |
| Number of pages | 5,415 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Visitors
| Traffic History 90 Day Average | ||
| Worldwide Rank | 1,505,599 |  -2,605,130 |
|---|---|---|
| Daily Visitors | 150 | +300% |
| Daily Visitors Rank | 1,663,437 | -3,342,156 |
| Daily Pageviews | 450 | +170% |
| Daily Pageviews Rank | 1,420,164 | -1,638,914 |
| Pageviews Per User | 4.00 |  -24.80% |
Content
www.Luckycraft.co.jp
- Popular pages
- luckycraft.co.jp NETWORK MEMBER'S - LUCKYCRAFT
- luckycraft.co.jp LUCKY CRAFT?|?LC lure fishing!
- luckycraft.co.jp New Products - LUCKYCRAFT
- luckycraft.co.jp PRODUCTS BASS - LUCKYCRAFT
- luckycraft.co.jp PRODUCTS - BEVY SHAD
The site has about 164 users daily, viewing on average 4.00 pages each.
Links- Links out
- geraldswindle.com Home | Gerald "G-Man" Swindle
- anthonygagliardi.com Anthony Gagliardi FLW Angler of the Year - Home
- luckycraft.jp LUCKY CRAFT U.S.A. - JAPAN
- youtube.com fishluckycraft's Channel - YouTube
| Server Location | |
| Ntt Communications Corporation Tokyo-to Tokyo Japan 35.69, 139.75 | |
Its local IP address is 120.29.170.229. ns1.secure.net, and ns2.secure.net are its DNS Nameservers. The server is hosted by Ntt Communications Corporation (Tokyo-to, Tokyo.)
IP: 120.29.170.229
| PING (120.29.170.229) 56(84) bytes of data. | |
| 64 bytes from (120.29.170.229): icmp_seq=1 ttl=47 | 158 ms |
| 64 bytes from (120.29.170.229): icmp_seq=2 ttl=47 | 144 ms |
| 64 bytes from (120.29.170.229): icmp_seq=3 ttl=47 | 163 ms |
| --- ping statistics --- | |
| 3 packets transmitted, 3 received, 0% packet loss, time 1999ms | |
| rtt min/avg/max/mdev = 144.114/155.313/163.582/8.213 ms | |
| rtt min/avg/max/mdev = 144.114/155.313/163.582/8.213 ms |
Pinging the server, resulted in a 158 ms response.