Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../archive/global.php on line 26

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 4912

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104

Warning: date() [function.date]: It is not safe to rely on the system's timezone settings. Please use the date.timezone setting, the TZ environment variable or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/Denver' for 'MDT/-6.0/DST' instead in ..../includes/functions.php on line 5104
Is this going to be new Force SUV or LWB Gurkha with 611?? [Archive] - 4wd4all

PDA

View Full Version : Is this going to be new Force SUV or LWB Gurkha with 611??



Rahul
04-08-2010, 04:47 PM
Well you read it here first. If you are copying this information would request you to link back to this site.



Guangdong FODAY Automobile Co., LTD. is the key automobile manufacturing enterprise authorized by National Development and Reform Commission, a new high-tech enterprise, and its production of complete vehicle can be traced back to 1988.

Guess this company is going to be preparing new SUV for Force Motors.
Source (http://www.fdqc.com/en/xinxi_detail.asp?id=1214)

" At the beginning of March, the Director and genaral manager of R&D department of Force Motors visited Guangdong Foday Automobile Co.,Ltd to promote the CKD cooperation.

Foday has contacted with Force Motors from 2008. then, the Chairman and director of Force Motors and several engineers visited Foday company in September with managers of ITOCHU company. Two vice general managers Mr.Ji and Mr Wang, the general manager of Marketing company Mr.Jiang, managers of R&D department and Technology department attended the negotiation meeting. Both parties presented cooperation intent. Later, two engineers was left for further basic study on the feasibility to match Foday’s Explorer III with Force Motor’s chassis.

Finally, we got conclusion that they can match once do a little correction.
Regarding there will be some confidential information to exchange, Force Motors and Foday have signed related documents.
Through the second visit, both parties agreed on the basic plan of the project. Force Motors will order the sample cars for study. The study process will finish in June as estimated by India company.

This project will become another successful case after the Iran project. As their plan, the production will reach at 800 units per month. At the same time, more and more africa countries have focused on our advantage in CKD business. We believe, the coming Canton fair will also bring us more opportunities. "

What do you think guys!!

Wanderer
04-08-2010, 04:50 PM
Goodbye Gurkha and Force for me, will stick to my relic Gurkha and the Tonka Toy HiLux. What makes me laugh is the word confidential on a blatant cheap Chinese copy of the Ford Endeavour.

talisker
04-08-2010, 08:49 PM
I´m not sure the embedded picture will be a new offroader. Because the Explorer III is a 2WD vehicle

http://www.fdqc.com/en/view.asp?xtitleid=8

Force may sell this vehicle in India, but I guess it will not be a 4x4 with OM611..

Cheers
Talisker

Rahul
04-08-2010, 09:42 PM
Talisker, the drivetrain would remain of OM611 and body is this, thats what they were talking about "Matching"

They say ... "Later, two engineers was left for further basic study on the feasibility to match Foday’s Explorer III with Force Motor’s chassis.

Finally, we got conclusion that they can match once do a little correction."

Wanderer
04-08-2010, 10:25 PM
It would be a difficult job to squeeze the existing Gurkha chassis into that body, from what I read, the Foday uses Mitsu chassis.

talisker
04-08-2010, 11:06 PM
Rahul, if that is the case, it should be great with a little more GC. Afterall people complained about refinement in Gurkha, which should be covered here. Doesnt matter if it is a cheap imitation of Endeavor, after all Gurkha body is a cheap imitiation of....

Good looks, refined vehicle and the proven Gurkha powertrain should be a solid package.

Wanderer, itś not the Gurkha chasis, instead the LWB Judo chasis (I´m guessing from the pic and the wheelbase)

Cheers
Talisker

Dr.Mohan
04-08-2010, 11:21 PM
No wonder Force is not at all marketing the current Gurkha.
Force thinks the current Gurkha is not worth marketing and there is nothing wrong in it. We look at Gurkha as the ultimate 4WD,but the general public has nothing to do with diff locks and the strong tubular chassis. It drools at the interiors,comforts ,looks and off course the performance.
So Good luck to Foday and Force..together they can make "Fodayce".

Rahul
04-08-2010, 11:30 PM
What I have read else where is that they are going to get body panels from Foday. Foday has got expertise in that regards.

The issue is will chinese panels be able to withstand the off-road shocks or even the nudges of rickshaw and cycle wala on road?

Also guess they are planning to use these panels as this would reduce the overall weight of Gurkha/LWB vehicle. AS well end up saving money for them as well.

Personally for me with this body am not ready to buy this vehicle even if 611 is there and that too market price indicative is 10+ lacs ex-showroom, raising it to 12-13 lakhs On the road.

Besides this, I am not very sure of Force people to handle the luxury or comfort part in a decent manner - they have never heard of it. As one force guy was telling me - they make vehicles for rural market only.

hisunil
04-09-2010, 08:57 AM
Hi Guys,

This is my first post here, hence a little intro:
I am Sunil Kumar from Bangalore & have been following the Gurkha for more than 4 years now. Want to buy one but not able to for various reasons.
Last I heard from the CSE in Bangalore is that they will leave the Gurkha AS IS w.r.t body & chassee (will get the 611 upgrade after its proven in Trax range),
but will launch this new vehicle in an SUV segment.

Thanks
Sunil

Wanderer
04-09-2010, 08:59 AM
Welcome Sunil.

Unfortunately even Force motor guys including the CEO have no idea of whats going on in their company and thats the truth, they will commit to something and then totally go back on it, thats been my experience and I have been dealing with them since 97. Therefore take everything they say with a extra dose of salt.

Wanderer
04-09-2010, 09:01 AM
Dr. Mohan,

If they were serious, Gurkha's market would be out of India, if they can price it below US$25,000 with the OM611, they will sell every one they can make in countries like US, South America and Europe where they are dying for a hardcore offroader with reliability.

Actually Foday+Force=Fodder thats what this current vehicle will be. Even with the OM611, they can't break into the dominant sector of MUV where Innova has firmly established its reputation, even if they price it below, no one is gonna buy a Fodder from Force motors.

Ankit
04-09-2010, 11:55 AM
I think the make or break will depend on the quality of the product. There are people who pay 10+lacs for a 4x4 Scorpio or Safari then why not this?

The pictures dont show a very stylish vehicle but if the actual vehicle is of the same quality or better than the Safari or Scorpio then it may have a market. After all I would assume that only the body and interiors will be FODAY and the rest will all be Force. Just because it is made in China dosent mean it has to be inferior quality (although china is famous for their cheap and inferior quality products).

Wanderer
04-09-2010, 01:19 PM
The problem here is conception and its implementation, Scorpio and Safari don't have the pedigree mechanicals of the Force vehicles but they went to Hawthal Whiting and got the exteriors and interiors done as well as implementing quality control in the assembly lines and parts quality control, so a Safari or Scorpio coming out of the factory is put together better than a Force product except for MAN. Its the mechanicals that keep Force afloat but now with this vehicle they are treading on established grounds with big players like Toyota's Innova which is a hallmark in this class as well as Tavera etc. This is not going to be easy going by Force's previous records.

gurkha
04-13-2010, 07:08 PM
now i'm little worried, can anyone tell me how long i can get spares for my gurkha.

ashwat.p
04-14-2010, 12:37 AM
Dont worry about spares till FORCE MOTORS is there spares will always be available. GOD GIVE FORCE SOME FORCE.

Wanderer
04-14-2010, 02:52 PM
Gods give Force to FORCE.

Rahul
04-14-2010, 11:39 PM
Did you guys saw the new pictures of Gurkha, it looks like gama, with silver cladding and even door handles of Gamma.


Power Steering as if it is something new!!
http://i901.photobucket.com/albums/ac215/rroy123/Alibagh%20OTR/PSGurkha.jpg

talisker
04-20-2010, 10:29 PM
Did you guys saw the new pictures of Gurkha, it looks like gama, with silver cladding and even door handles of Gamma.


Rahul, even my Gurkha has the same door handle. Mine was the first one from the new gen stable and it has the old instrument cluster, old door handle and biege interior, hydraulic diff-locks, Apollo ranger highway tyre and spare being JK LT2000 :eek:

Apart from the engine, GB, T-case, wheelbase and chasis, everything else depends on their mood and are subject to change

Cheers
Talisker

ashwat.p
04-22-2010, 01:19 AM
Hi, Talisker where are you from. How is your gurkha

Rahul
04-22-2010, 01:35 AM
Talisker is one of the first people to get the new Gurkha.

talisker
04-22-2010, 10:22 PM
Hey Ashwat, Iḿ from Bangalore.

Yes, I started chasing Force for a 4x4 with diff lock product in 2006, got fed up after several months or so, booked a Gama 4x4. Then Gurkha was announced privately to some of us and I ended up committing the entire money to them with the vehicle delivered 11 months later. The effort was nothing short of a penance.

Cheers
Talisker

Ankit
04-23-2010, 03:56 PM
Talisker is one of the first people to get the new Gurkha.

What is "New" about the new Gurkha?

ashwat.p
04-24-2010, 02:07 AM
http://www.rushlane.com/125562/spy-shots-force-motors-suv-spotted.html

gurkha
05-27-2010, 11:02 AM
congratulations talisker, can we look forward for some more pics of ur gurkha ( including interiors)

Ankit
06-10-2010, 07:21 PM
No News on this for a long time.

Any upadates you have Rahul? Is the plan to launch this still on?

Cheers
Ankit

Rahul
06-10-2010, 10:59 PM
I have stopped chasing Force. They make good machines, but good marketing is not in their forte. Good engineers bad managers :(

talisker
06-23-2010, 10:50 AM
The news is indeed true, but Alas, no launch dates as of yet. I happened to see the pictures at Force dealership and it pretty much resembles what has been shared in this forum. Chinese body and interiors on a Trax mechanicals.

Happened to catch up with an ex-Force employee who held a high position and he mentioned that OM611 has very positive response and customers are loving it. Apparently a modified 5-Cyl DI version of OM617 is being planned.

Again, with all these news, WHEN is a a big question mark :confused:

Cheers
Talisker

Rahul
06-28-2010, 11:29 AM
I hope I get to see those in this lifetime!

talisker
10-02-2010, 12:18 PM
Now what is going on here ??? :rolleyes: Could this be based on some news about this new SUV catering to mass market ??

2443

Cheers
Talisker

Rahul
10-02-2010, 12:39 PM
I doubt the news. It must be the MAN thing and the new TT.

Think about a 1990 engine, is not going to set sales on fire, when coupled with Chinese body. I actually have lost all interest for the new Gurkha.

Wanderer
10-02-2010, 01:06 PM
The engine itself is far superior to the Toyota Fortuner engine and even though has less bhp, it has longer life, better torque and way more refined than the tractor engine used in the Toyota, so engine vintage is not an issue here, the FODAY body is :(

Ankit
10-02-2010, 04:10 PM
The way the automobile industry is growing right now I would have expected this to be a right time for the launch for a vehicle which is around 10L with the space of an endevour and practicality of a 4x4 + diff locks and the super OM611 engine. Built quality would be the only suspect.

Cheers
Ankit

talisker
10-02-2010, 07:24 PM
I doubt the news. It must be the MAN thing and the new TT.

Think about a 1990 engine, is not going to set sales on fire, when coupled with Chinese body. I actually have lost all interest for the new Gurkha.

Hmmm. maybe, but it is a big jump in share price..!

It wont be a Gurkha for sure, it's just a Chinese body mated with OM611 and Force mechanicals. There are spy pics all over the web.

Not sure if it will set sales on fire, but for sure it will interest buyers who knows the OM6xx lineage

Cheers
Talisker

scphanse
10-02-2010, 09:48 PM
The news is indeed true, but Alas, no launch dates as of yet. I happened to see the pictures at Force dealership and it pretty much resembles what has been shared in this forum. Chinese body and interiors on a Trax mechanicals.

Happened to catch up with an ex-Force employee who held a high position and he mentioned that OM611 has very positive response and customers are loving it. Apparently a modified 5-Cyl DI version of OM617 is being planned.

Again, with all these news, WHEN is a a big question mark :confused:

Cheers
Talisker

Talisker any timelines for the 611 or 617?
Do you have any pics of the "chinese model" Trax?
How long do you suggest I shld wait?

I know too many question, but with that post above this was bound to happen.
- salil

Wanderer
10-02-2010, 10:27 PM
If the engine makes it to Gurkha, it will turn it into one potent off roader that will go toe to toe with any in the international market.

talisker
10-03-2010, 01:15 PM
Talisker any timelines for the 611 or 617?
Do you have any pics of the "chinese model" Trax?
How long do you suggest I shld wait?

I know too many question, but with that post above this was bound to happen.
- salil

Salil, It is expected by end of 2010, atleast thats what Firodia said in an auto journal. Gurkha was launched during Diwali 2007, so I assume around the same time this year.

It is based on Foday Explorer and here are the pics of this vehicle --> http://chinaautoweb.com/car-models/foday-explorer/

Mind you, there is no news if this vehicle will be available in 4x4 variants.

Cheers
Talisker

Freddystan
10-04-2010, 02:09 PM
Salil, It is expected by end of 2010, atleast thats what Firodia said in an auto journal. Gurkha was launched during Diwali 2007, so I assume around the same time this year.

Cheers
Talisker

I spoke to one of the managers at Khivraj last week when I had taken the judo for service and saw the actual pics of the vehicle. Finally the OM 611 has made its way into our market, mated with a 5 speed G32 gear box. A 4wd version is definitely in the pipeline but not anytime soon. He wasnt able to give me the exact specs but it will be somewhere arnd 130 BHP & 400 NMs of torque...Man thats something aint it!!! Trust me, no one would ever know it runs on a merc derived engine without aggressive marketing, the kind of reputation Force has, they will have to play out of their skins to compete with the likes of Fords & toyotas... BTW its about to be launched by the end of this year..

Wanderer
10-04-2010, 02:20 PM
At 400NM torque, there will be many sad Scorpio, Safari and even Fortuner egos on the road. :)

Ankit
10-04-2010, 02:44 PM
I spoke to one of the managers at Khivraj last week when I had taken the judo for service and saw the actual pics of the vehicle. Finally the OM 611 has made its way into our market, mated with a 5 speed G32 gear box. A 4wd version is definitely in the pipeline but not anytime soon. He wasnt able to give me the exact specs but it will be somewhere arnd 130 BHP & 400 NMs of torque...Man thats something aint it!!! Trust me, no one would ever know it runs on a merc derived engine without aggressive marketing, the kind of reputation Force has, they will have to play out of their skins to compete with the likes of Fords & toyotas... BTW its about to be launched by the end of this year..

Any news on the price bracket? Bit dissapointed that there will be no 4x4 option. Most SUV buyers who buy 2wd buy it for the road presence an snob value, which is something Force lacks. The snob value in Force is it's 4x4 and diff lock, et all so whithout this what is the point?

Just my view.

Cheers
Ankit

Wanderer
10-04-2010, 02:50 PM
Absolutely right Ankit, Gurkha is the bread and butter of Force, not a Innova clone, no one will buy that from Force, MB engine notwithstanding.

Freddystan
10-04-2010, 03:01 PM
Any news on the price bracket? Bit dissapointed that there will be no 4x4 option.

Cheers
Ankit

Around the 16Lack bracket, aggressively prices along side the Endeavour is what he said and it also resembles one to a great extent..

Ankit
10-04-2010, 03:18 PM
Around the 16Lack bracket, aggressively prices along side the Endeavour is what he said and it also resembles one to a great extent..

I seriously doubt that Force will be able to sell this for 16L, that too without a 4wd option. I was expecting 10L to 12L.

The non-4wd Ford Endeavour 2.5L TDCI produces 143PS@3500rpm, 330Nm@1800rpm and costs 16.4L ex-showroom. Would you spend the same and buy a chinese Force?

Ask a non-4wd enthusiast SUV buyer if what they are willing to pay for a Chinese developed SUV with Merc engine & GB built by Force Motors and I am sure it will be nowhere near that amount. Maybe closer to a top end Scorpio but nothing more.

Cheers
Ankit

Wanderer
10-04-2010, 06:27 PM
Ankit is correct, even though the MB engine is miles ahead of the Ford's 16L is quite optimistic for a Force SUV.

Rahul
10-05-2010, 02:57 AM
At 400NM torque, there will be many sad Scorpio, Safari and even Fortuner egos on the road. :)

OM611 never ever produced 400 nm torque. Maximum what they were able to get was

OM 611 inline four 16v DOHC 2,148 cc (131.1 cu in) 129 PS (95 kW; 127 hp) 300 N·m (221 ft·lbf)

I seriously doubt given the reputation in workmanship, who would spend 10+ for a Chinese body. Bruised egos would be of just Gurkha owners, who have grayed their hair waiting for Gurkha in 611 avatar with this ancient engine!

Wanderer
10-05-2010, 07:00 AM
Thats what I thought, 400NM sounded to be a optimistic number, ancient engine or not, its far more refined that the tractor engine in the Fortuner, in fact the 72 vintage OM616 and 617 sound and run more refined that any of the diesels put in Toyota. Looks like Toyota needs a civility lesson from MB, also the 611 gets an industry standard warranty in the US and therefore I expect it to outlast any of the current diesels being sold here in India which includes Toyo and Mitsu, of course all this is a moot point if it doesn't get introduced in the Gurkha.

talisker
10-05-2010, 10:25 AM
Yes, had seen the pictures at Mangalore Force several months ago, and it's nothing but Foday Explorer. The price that was told to me was 10-14 ex-showroom. Probably 16L was on the road price for a high end model.

400NM is over optimistic number, unless they have tweaked the engine to that extent. Remember, new gen engines are always undertuned to have some tolerance levels. Which is very much needed with the quality of fuel we get + the lethargic mechanics who are prone to do mistakes.

Current Gurkha engine can be easily tuned to produce 250NM+ by changing the mapping in the Bosch EDC without causing ANY harm to the engine.

Cheers
Talisker

Wanderer
10-05-2010, 10:28 AM
I got another news for you, the Finns fit modded myrna pumps and turbo to OM617 to get 350 reliable BHP and on OM616 turbo around 260bhp with ease,thats the potential of these engines, unlike others, they have severe duty tolerances.

scphanse
10-05-2010, 06:59 PM
16L without 4wd- are they Joking?????

Wanderer
10-05-2010, 10:01 PM
Rather being overtly optimistic.

scphanse
10-06-2010, 02:28 PM
Rather being overtly optimistic.

Wanderer I agree wholeheartedly with you.

I hope they are not going to kill the Gurkha in its present avatar when they launch the Fodoya or whatever toy?

Wanderer
10-06-2010, 04:41 PM
Don't be surprised if they do, anyways, they have always been halfhearted on the Gurkha project, initially it was perfect with the right engine, just needed quality workmanship which is an utopia at Force. Then they needed to market it right and support and back it up, couple of world events and Gurkha would have been ultimate. They had the perfect concept for probably one of the greatest off roader only to murder it with their apathy just like VFJ did with the venerable Jonga.

scphanse
10-06-2010, 06:52 PM
I cannot but agree with that. The only problem is I hope they dont strangle it before my budget allows me buying one.

talisker
10-07-2010, 09:43 AM
I cannot but agree with that. The only problem is I hope they dont strangle it before my budget allows me buying one.

If they dont, then the govt will. BS2 vehicle production in India is ceased from Sept 30th. Current Gurkha is BS3, so not sure when the end date is..!!

Cheers
Talisker

scphanse
10-07-2010, 11:25 AM
Today seems to be a bad day for me....:( Nevertheless if the production of Gurkha is stopped what about spares?
Would it be a good idea to go in for a used car in good condition? (if one can lay ones hand on such a vehicle); considering Gurkhas for second sale seem to be rarer than the dodo bird.

Wanderer
10-07-2010, 11:37 AM
Apart from the front diff arrangement, Gurkha uses everything else from standard Trax, Tempo Traveler parts bin so it shouldn't be an issue.

talisker
12-08-2010, 09:47 PM
All,

Check this picture out and pay particular attention to Engine, Gearbox and tyres..:rolleyes:

Now what have we done wrong so this config is not available here ?

3700

Cheers
Talisker

scphanse
12-08-2010, 09:57 PM
We surely are cursed. Or are we just Children of a lesser god????
Is there not anyway to lay our hands on one of these??

Dr.Mohan
12-08-2010, 11:35 PM
yeah there is a way..a roundabout way..import these in India .

talisker
12-09-2010, 07:35 AM
They seem to be mounting OM611 and G32/5 gearbox on the same chassis which gives an option for anyone eyeing at an upgrade in the near future.

Anyone having contacts at Force can confirm why this option was not considered for Indian market. I'm sure it must be the CMVR rules and the limited customer base.

Cheers
Talisker

Rahul
12-09-2010, 12:27 PM
Talisker I had taken these ads to Mr. Bellary and Mr. Magoon in Pune. They said it is not true. This you have got from one US site ecomobil or something like that. I was pretty dismayed when I saw these two years back. Had it been true guess then things would have been quite different here at force.

scphanse
12-09-2010, 02:03 PM
yeah there is a way..a roundabout way..import these in India .
Sir, If I had that kind of Outlay at my disposal, would not have been thinking of buying a second hand and doing it up..... :(

Hence, request your advise on the Tempo Trax Town & Country thread I started.

talisker
12-09-2010, 07:43 PM
Rahul, what you say might be true as well, cos nowhere they have mentioned it as a Force product. Not even front grill has Force Symbol :confused:

Cheers
Talisker

ashwat.p
03-10-2011, 12:07 AM
This is the new SUV from FORCE Motors. Lets see how well does it perform. As said earlier God give FORCE some force.

Snipervib
03-10-2011, 08:33 AM
OMG the car above is soo damn ugly ...force is gone old korean with the looks

Ankit
03-10-2011, 10:19 AM
Are these pics of the Chinese variant? What is the drivetrain on it in China?

Any news from Force?

Cheers
Ankit

ashwat.p
03-11-2011, 12:08 AM
These pictures got from the Foday website, they run on ISUZU engine with technology from BOSCH. Didnt read much in detail. When Force has collabaration with Dailmer and MAN why did it source body from China. They could designe themselves but the cost factor comes in.

scphanse
04-04-2011, 10:55 PM
saw the heavily camauflaged new offering from Force today- even in camouflage it looks revolting
Was been driven around by a family of four. Don't tell me that Force has now started getting its top execs to test drive the vehicle. When I asked to peek inside the gentleman was downright rude. Was about to give a earful myself when my wife intervened (Thank heavens for small mercies).
I would have thought that Force, if trying to bring out a new SUV could atleast be nice to people interested in the vehicle.
Just my 2 bits.... :)
regards
salil
PS: Has production of the Gurkha stopped?

Freddystan
05-02-2011, 07:47 PM
This is an ongoing discussion for years, stumbled upon this article on the Force website. Will Force be able to manage ASS in this segment with the current dealership network?? The service centres just dont seem to be equipped to handle the upmarket crowd. Also attached is a PDF version.


FORCE MOTORS TO LAUNCH PREMIUM SUV THIS YEAR

Force Motors, the Pune-based automotive company earlier called Bajaj Tempo, would take a plunge into the two million-strong passenger vehicle market for the first time later this year, with the launch of a sport utility vehicle (SUV) positioned in the upper-mid segment.
The Abhay Firodia-led Company, which makes tractors, three-wheelers, light and heavy trucks, has indigenously developed an SUV that will be positioned in the Rs 10-15 lakh bracket. This price segment does not have any players presently, with the exception of higher variants of Tata's Safari and Mahindra's Scorpio.
Force Motors has even sourced a Daimler engine (the company owns the Mercedes brand of vehicles) to be fitted in the new SUV. This new vehicle, which has been built on an entirely new platform developed by the company, will come with the option of seating five to seven people.
Parts from outside
To keep costs down, the company has decided to source certain, but not critical, parts for the SUV from outside India, mainly from Chinese or Taiwanese suppliers. Plastic parts for the interiors may fall under this agreement, according to a senior company executive.
Prasan Firodia, managing director, Force Motors, said, “A substantial part of the vehicle has been developed in-house using indigenous expertise. We are targeting the final months of this (calendar) year or the early months of next year.”
Usually a new product developed from scratches, including the platform and the additions made to the manufacturing plant (except for a volume generating vehicle), costs Rs 600-800 crore. The company declined to provide financial details of the project.
The new SUV would be produced at the company's Pithampur plant in Madhya Pradesh, from where it also makes heavy trucks in association with MAN Nutzfahrzeuge, one of Germany's largest commercial vehicle makers. Force and MAN hold equal stakes in the joint venture company called Man Force Trucks, which makes the trucks.
Despite having a variety of products under its fold, Force Motors has a negligible share of 0.15 per cent of the domestic auto market. The company is better known in the passenger three-wheeler space, with products having its popularity in the interiors of the country.
It recently launched a four-wheeled light cargo vehicle called the Trump to compete against products such as Tata Motors Ace and Mahindra Maxximo. The company produces mini-buses and multi-seater passenger vehicles.

Rahul
05-02-2011, 10:33 PM
I have become quite skeptical about Force motors's promises.

Keeping my fingers crossed over their product and the promises they make.

thompsonmike
05-11-2011, 11:46 AM
I have good informal news that Force is about to launch an SUV in 10L segment. How much truth is there in this news.

Abdul Gafur
05-19-2011, 06:53 PM
I have good informal news that Force is about to launch an SUV in 10L segment. How much truth is there in this news.

Its very true …. I have gone through couple of articles on this SUV: I think with a Merc Engine it should comfortably go upto 160 kmph to 170kmph, Somewhere btwn 10 to 12 kmpl, fully loaded vehicle… Expected around July'11 & will have around 50 dealerships..:o

scphanse
05-20-2011, 01:49 AM
10L is fine. BUT what are they offering for 10L??
Only Vanilla will have no takers, not from Force atleast. The company is making a huge outlay on the Showrooms I understand.
regards
salil

Freddystan
05-20-2011, 11:17 PM
Its surely out anytime now, I had visited the authorized guys a few days back and man, have they given that age old place a facelift!!! Just to handle the upmarket crowd, and there is a team of mechanics officially trained and have tested the vehicle as well. They told me that its a BS4 engine with an intercooler, I also got to see the new CRD Traveller, super queit and packs some serious punch, really impressed with the new powertrain.

scphanse
05-24-2011, 12:07 AM
Its surely out anytime now, I had visited the authorized guys a few days back and man, have they given that age old place a facelift!!! Just to handle the upmarket crowd, and there is a team of mechanics officially trained and have tested the vehicle as well. They told me that its a BS4 engine with an intercooler, I also got to see the new CRD Traveller, super queit and packs some serious punch, really impressed with the new powertrain.

Hey Freddy,
Any details on the powertrain and pricing as of now???
regards
salil

Freddystan
05-24-2011, 11:52 PM
No idea, the insiders are quite naive or maybe just a pretense.. Its the very same engine as in the new traveller (OM 611 derived). Im seeing a futuristic gear lever for the FIRST TIME in a force vehicle and looks like it shifts like butter...Im posting some pics of the new CRD TT, BTW this is BS3 and the intercooled BS4 will power the new SUV.

49254926492749284929

Abdul Gafur
06-04-2011, 03:26 PM
i dont think you are keeping urself updated enough tht is y u are askng this questn so late. There are so many articles and blogs praising this product because of Merc 2.2 lts engine, whole electronic mapping done from merc, Ride and handling is finetuned by Lotus engineering, UK. There is no connection of this product being a chinese product, infact technologically it is the best in the segment of 10-12 lacs

First of all you tell me who told u it can be LWB Gurkha with 611. Are u kiding me…? This car is build in house by force motors. Read the interview article of MD of force motors. It will run on Merc 2.2 ltr engine. Whole electronic mapping is done by Merc and Ride & handling is finetuned by Lotus engineering, UK. (I hope you knw Lotus engineering... LolZ..)

dude… u trY to Peek in any test vehicle,, u will be treated very rudely. Y will they allow you to c the vehcle frm insyd whn it is camauflaged. They have done so much of hard work to create. Y u will become a VIP to c it bfre anyone else.. HhahahaHAHa.. Still u have askd this query so i will try to help u as i read intervw article of force motors MD and some info on blogs.. this SUV have a sze like Endevour, wl run on 2.2 lTr Merc Engine, Ride and handling will be superb as it is finetuned by Lotus engineering, Price b/w 10-12lac. it will be launched very soon (July, 11) so calm down and thn c the vehicle in a proper shape.

scphanse
06-04-2011, 09:38 PM
Dear Abdul,
By any chance are you with Force Motors?.... :) Your posts or rather the timbre of your posts suggest so.... ;)
regards
salil

hisunil
06-05-2011, 06:33 PM
Hi Abdul Gafur,

Welcome to 4wd!
Please introduce yourselves, by starting a thread in the Introductions section.

Fred is helping us by brining in Live data from local workshops,
I guess the lease we can do is to Thank him & add other info resources .

Cheers
Sunil

Rahul
06-06-2011, 12:23 PM
Hi Abdul,

2.2 L merc OM611 is almost a decade old engine, nothing too great to harp about it. I do not know what kind of relations you enjoy with force motors, but I have been using Gurkha since 2008. My haggling with Force motors started in 2006, and every three months I was told that 611 is being released. It never did so got my DI Gurkha in 2008.

The engine is not in use by Merc. on any of it's vehicle. Lotus has worked on Scorpio suspensions, so does that makes it best in the world?

Why the vehicle wont be Gurkha, as pointed out by you

SUV size of Endeavor - Gurkha had always been SWB, the LWB was known as JUDO. So this SUV is not Gurkha.

If you probe further, then you will know even the chassis design is different of this SUV and Gurkha, I hope you know what is the difference!

Yes the body panels are from China.

With the given network of force motors, parts supply, and attitude - I guess I am not in line to spend 12 lacs amount just for the engine!

What do you think Abdul?

Freddystan
06-07-2011, 12:54 AM
Hi Abdul,
Welcome to the Forum, the info you have shared are mere internet extracts and everyone here im sure have hrd all of this in bits and pieces. You definitely seem to know more than the manufacturers themselves, why dont you share some finer aspects and contribute to our cause. Afterall being a critic is good, but not without valuable contribution.

Abdul Gafur
06-08-2011, 07:02 PM
Are these pics of the Chinese variant? What is the drivetrain on it in China?

Any news from Force?

Cheers
Ankit

Yes the above pics belongs to the Chinese vehicle which is named as Forday ExplorerIII, the original pics are updated in this thread also which are covered with clothes. Force SUV is going to be launched in July with all bells & whistles with it
Cheers
Abdul

talisker
06-15-2011, 10:57 AM
Fred, slightly OT, but when did you visit Khivraj ? I was there last saturday and understood that the entire workforce is striking for better pay. I could see that they are constructing a brand new showroom in Yeshwantpur probably gearing up for a new launch.

Rahul, How is your vehicle now ? Is it on road or with the A.S.S still ?

Cheers
Talisker

Freddystan
06-15-2011, 11:19 AM
Fred, slightly OT, but when did you visit Khivraj ? I was there last saturday and understood that the entire workforce is striking for better pay. I could see that they are constructing a brand new showroom in Yeshwantpur probably gearing up for a new launch.

Rahul, How is your vehicle now ? Is it on road or with the A.S.S still ?

Cheers
Talisker

I was there on May 19th to correct a T Case lever vibration. You are right, there is a huge display area coming up at the Yeshwanthpur service centre, Alla Bakhash, the Gurkha saviour is now trained on the new engines..

Dr.Mohan
06-17-2011, 01:42 AM
My honest Opinion: We still do not know for sure how the new SUV looks and sounds like. If the pictures are to be believed , I dont think the vehicle looks that bad. Had it been a 4wd version I surely would have booked one. Okay dont throw bricks at me......

Rahul
06-17-2011, 08:57 AM
I am seriously thinking of used Excel 4x4 after my trip to Leh. Even if this vehicle is with 4x4 I will still have to be gifted many things now since it is a vehicle from "FORCE" with not enough Force from them.

mailtopps
06-24-2011, 12:17 PM
Did you guys saw the new pictures of Gurkha, it looks like gama, with silver cladding and even door handles of Gamma.


Power Steering as if it is something new!!
http://i901.photobucket.com/albums/ac215/rroy123/Alibagh%20OTR/PSGurkha.jpg

I guess the power steering and power "break" is a big turn on for the village folk and the politicians