Krbamboo.com
Krbamboo is ranked 13,820,318 in the United Kingdom. 'Contact-Shenzhen Kanger Bamboo & Wood Co., Ltd.'
13,820,318Rank in United Kingdom
9,719,811Worldwide Rank
Monthly pages viewed | 3,780 | |
Monthly visits | 1,890 | |
Value per visitor | -- | |
Estimated worth | £978.59 | |
External links | 21 | |
Number of pages | 195 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Visitors
Traffic History 90 Day Average | ||
Worldwide Rank | 8,167,908 | -20,158,507 |
---|---|---|
Daily Visitors | 24 | +1000% |
Daily Visitors Rank | 7,887,247 | -20,382,356 |
Daily Pageviews | 0 | +2000% |
Daily Pageviews Rank | 9,387,922 | -18,950,894 |
Pageviews Per User | 1.50 | +50% |
Content
www.Krbamboo.com
Age: The domain is 13 years and 2 months old.
- Popular pages
- krbamboo.com Contact-Shenzhen Kanger Bamboo & Wood Co., Ltd
- krbamboo.com Shenzhen Kanger Bamboo & Wood Co., Ltd
- krbamboo.com -General Information-Shenzhen Kanger Bamboo & Wood Co., Ltd
- krbamboo.com Shenzhen Kanger Bamboo & Wood Co., Ltd
- krbamboo.com Patent Locking System-Patent Locking System Bamboo Flooring ..
26 users visit the site each day, each viewing 1.50 pages.
Links- Links out
- 36099.com ??????|????|??????????
- 2345woool.com ????,??????,2345woool?????????
- 456baike.com ??????,????,?????????
- zblbt.com ????,??????,??????,????
Server Location | |
Nwt Idc Data Service Kowloon Hong Kong 22.32, 114.18 |
f1g1ns1.dnspod.net, and f1g1ns2.dnspod.net are its DNS Nameservers. The server is hosted by Nwt Idc Data Service Kowloon. Krbamboo.com's server IP number is 58.64.172.164.
IP: 58.64.172.164
PING www. (58.64.172.164) 56(84) bytes of data. | |
64 bytes from 58.64.172.164: icmp_seq=1 ttl=112 | 225 ms |
64 bytes from 58.64.172.164: icmp_seq=2 ttl=112 | 214 ms |
64 bytes from 58.64.172.164: icmp_seq=3 ttl=112 | 213 ms |
--- www. ping statistics --- | |
3 packets transmitted, 3 received, 0% packet loss, time 2017ms | |
rtt min/avg/max/mdev = 213.278/217.711/225.740/5.712 ms | |
rtt min/avg/max/mdev = 213.278/217.711/225.740/5.712 ms |
Pinging the server, resulted in a 225 ms response.