Tribal Wars Statistieken: nl48: Player
Tribalwars-spelersprofiel: worst case scenario
Datum | Speler | Stam | Rang | Punten | Dorpen | Tegenstander Verslagen | Tegenstander Verslagen - Aanvaller | Tegenstander Verslagen - Verdediger |
---|---|---|---|---|---|---|---|---|
2017-01-04 | worst case scenario | Guard | 50. | =673,634 | =73 | =6,666,745 | =6,183,864 | =157,238 |
2017-01-03 | worst case scenario | Guard | 50. | +673,634 | =73 | =6,666,745 | =6,183,864 | =157,238 |
2017-01-02 | worst case scenario | Guard | 50. | +673,436 | =73 | +6,666,745 | +6,183,864 | +157,238 |
2017-01-01 | worst case scenario | Guard | 50. | +672,114 | =73 | +6,210,469 | +5,919,929 | =156,568 |
2016-12-31 | worst case scenario | Guard | 50. | +670,474 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-30 | worst case scenario | Guard | 50. | +669,334 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-29 | worst case scenario | GM | 49. | +667,790 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-28 | worst case scenario | GM | 49. | +666,206 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-27 | worst case scenario | GM | 49. | +665,522 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-26 | worst case scenario | GM | 49. | +663,874 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-25 | worst case scenario | GM | 51. | +662,535 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-24 | worst case scenario | GM | 51. | +660,876 | =73 | =6,206,647 | =5,916,332 | =156,568 |
2016-12-23 | worst case scenario | GM | 51. | +658,271 | =73 | +6,206,647 | +5,916,332 | =156,568 |
2016-12-22 | worst case scenario | GM | 52. | +656,971 | =73 | =6,142,867 | =5,852,552 | =156,568 |
2016-12-21 | worst case scenario | GM | 52. | +655,250 | =73 | +6,142,867 | +5,852,552 | =156,568 |
2016-12-20 | worst case scenario | GM | 52. | +652,402 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-19 | worst case scenario | GM | 53. | +650,321 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-18 | worst case scenario | GM | 53. | +648,264 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-17 | worst case scenario | GM | 54. | +645,824 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-16 | worst case scenario | GM | 55. | +642,710 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-15 | worst case scenario | GM | 55. | +640,591 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-14 | worst case scenario | GM | 55. | +639,460 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-13 | worst case scenario | GM | 56. | +638,306 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-12 | worst case scenario | GM | 55. | +635,224 | =73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-11 | worst case scenario | GM | 55. | +632,128 | +73 | =5,816,970 | =5,526,655 | =156,568 |
2016-12-10 | worst case scenario | GM | 55. | +627,813 | +72 | +5,816,970 | +5,526,655 | =156,568 |
2016-12-09 | worst case scenario | GM | 57. | +621,055 | =66 | +5,816,951 | =5,526,647 | =156,568 |
2016-12-08 | worst case scenario | GM | 56. | +620,377 | +66 | +5,787,188 | +5,526,647 | =156,568 |
2016-12-07 | worst case scenario | GM | 57. | +613,548 | =65 | +5,786,617 | +5,526,295 | =156,568 |
2016-12-06 | worst case scenario | GM | 57. | +612,976 | =65 | +5,786,546 | +5,526,247 | =156,568 |
2024-05-19 15:22:18 CEST