Flottweg.com
Flottweg is ranked 555,172 in the United Kingdom. 'FLOTTWEG DECANTERS, DISC STACK CENTRIFUGES AND BELT PRESSES IN ..'
555,172Rank in United Kingdom
3,416,185Worldwide Rank
| Monthly pages viewed | 19,656 | |
| Monthly visits | 1,119 | |
| Value per visitor | £0.19 | |
| Estimated worth | £745.79 | |
| External links | 267 | |
| Number of pages | 600 |
Last Updated: 05/04/2018 . Estimated data, read disclaimer.
Visitors
| Traffic History 90 Day Average | ||
| Worldwide Rank | 2,870,744 |  1,679,725 |
|---|---|---|
| Daily Visitors | 56 | -76.90% |
| Daily Visitors Rank | 3,774,258 | 2,573,189 |
| Daily Pageviews | 300 | -33.33% |
| Daily Pageviews Rank | 1,724,603 | 360,493 |
| Pageviews Per User | 8.00 |  +190% |
Content
www.Flottweg.com
Category: 'Separators/Centrifuges'
Age: The domain is 21 years and 7 months old.
- Popular pages
- flottweg.com FLOTTWEG DECANTERS, DISC STACK CENTRIFUGES AND BELT PRESSES IN ..
- flottweg.com for municipal waste and industrial water treatment
- flottweg.com Flottweg AG - Separation Technology
- flottweg.com Innovative Centrifuge Technology for plastics recycling
- flottweg.com RZ FLOT Tricanter
On average 8.00 pages are viewed each, by the estimated 61 daily visitors.
Server| Server Location | |
| Internetwire Communications Gmbh Muenchen Germany 48.1500015258789, 11.5832996368408 | |
Its web server is located at Internetwire Communications Gmbh Muenchen. It has 4 nameservers, including ns3.netservice24.de, ns4.netservice24.de, and ns1.netservice24.de. Its IP Number is 89.250.140.27.
IP: 89.250.140.27
| PING (89.250.140.27) 56(84) bytes of data. | |
| 64 bytes from www. (89.250.140.27): icmp_seq=1 ttl=54 | 114 ms |
| 64 bytes from www. (89.250.140.27): icmp_seq=2 ttl=54 | 114 ms |
| 64 bytes from www. (89.250.140.27): icmp_seq=3 ttl=54 | 114 ms |
| --- ping statistics --- | |
| 3 packets transmitted, 3 received, 0% packet loss, time 2001ms | |
| rtt min/avg/max/mdev = 114.049/114.158/114.246/0.287 ms | |
| rtt min/avg/max/mdev = 114.049/114.158/114.246/0.287 ms |
Pinging the server, resulted in a 114 ms response.