Startseite » Sport

Sport

  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /homepages/40/d360138574/htdocs/cms/modules/views/handlers/views_handler_argument.inc on line 744.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • warning: Creating default object from empty value in /homepages/40/d360138574/htdocs/cms/modules/taxonomy/taxonomy.pages.inc on line 33.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 14256 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 13774 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 13753 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 13751 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 13393 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 12781 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 12767 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 12766 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 12742 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT e.event_start, e.event_end, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM event e INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE nid = 12664 in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 12.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Declaration of views_handler_argument::init() should be compatible with views_handler::init(&$view, $options) in /homepages/40/d360138574/htdocs/cms/modules/views/handlers/views_handler_argument.inc on line 744.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: Non-static method view::load() should not be called statically in /homepages/40/d360138574/htdocs/cms/modules/views/views.module on line 906.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 1554.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 1557.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 1004.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 1004.
  • user warning: You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near 'offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start ...' at line 1 query: SELECT n.nid, n.uid, n.title, n.type, e.event_start, e.event_start AS event_start_orig, e.event_end, e.event_end AS event_end_orig, e.timezone, e.has_time, e.has_end_date, tz.offset AS offset, tz.offset_dst AS offset_dst, tz.dst_region, tz.is_dst, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_start_utc, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND AS event_end_utc, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_start_user, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 0 SECOND AS event_end_user, e.event_start - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_start_site, e.event_end - INTERVAL IF(tz.is_dst, tz.offset_dst, tz.offset) HOUR_SECOND + INTERVAL 3600 SECOND AS event_end_site, tz.name as timezone_name FROM node n INNER JOIN event e ON n.nid = e.nid INNER JOIN event_timezones tz ON tz.timezone = e.timezone WHERE n.status = 1 AND ((e.event_start >= '2025-09-30 00:00:00' AND e.event_start <= '2025-11-01 23:59:59') OR (e.event_end >= '2025-09-30 00:00:00' AND e.event_end <= '2025-11-01 23:59:59') OR (e.event_start <= '2025-09-30 00:00:00' AND e.event_end >= '2025-11-01 23:59:59')) GROUP BY n.nid HAVING (event_start >= '2025-10-01 00:00:00' AND event_start <= '2025-10-31 23:59:59') OR (event_end >= '2025-10-01 00:00:00' AND event_end <= '2025-10-31 23:59:59') OR (event_start <= '2025-10-01 00:00:00' AND event_end >= '2025-10-31 23:59:59') ORDER BY event_start ASC in /homepages/40/d360138574/htdocs/cms/modules/event/event_database.mysql.inc on line 104.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 679.
  • strict warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 679.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2759.
  • strict warning: mktime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting 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 'Europe/Berlin' for 'CET/1.0/no DST' instead in /homepages/40/d360138574/htdocs/cms/modules/event/event.module on line 2760.

Challenge Kraichgau

Verfasst von Gast am 11. Juli 2013 - 10:33
00.00.
Array

Die 90 km lange Radstrecke der Challenge Kraichgau führt durch die Ortsteile Büchig und Bauerbach. In Büchig befindet sich eine Verpflegungsstation an der die Radler mit Getränken, Obt und Müsliriegel versorgt werden. Außerdem ist eine Penaltybox an der Strecke nach Büchig.

In Bauerbach wird das Können der Radler durch eine spitze Kurve in der Ortsdurchfahrt auf die Probe gestellt.

Ort: OT Büchig, Bauerbach

Veranstalter: Kraichgau Sports Promotion UG

»

Sportlerehrung

Verfasst von Gast am 11. Januar 2013 - 9:15
00.00.
Array

Ehrung verdienter Sportler des Jahres 2012 durch die Stadt Bretten

Ort: Hallen-Sportzentrum Bretten, Max-Planck-Str. 3

Veranstalter: Stadt Bretten

»

Sparkasse Kraichgau CityCup Bretten

Verfasst von Gast am 27. Dezember 2012 - 11:32
00.00.
Array

Ort: Startpunkt Georg-Wörner-Straße vor dem Simmelturm

Veranstalter: Turnverein 1846 Bretten e.V

http://www.citycup-bretten.de/

»

Challenge Kraichgau

Verfasst von Gast am 27. Dezember 2012 - 11:27
00.00.
Array

Ort: OT Büchig, Bauerbach

Veranstalter: Kraichgau Sports Promotion UG

http://www.challenge-kraichgau.com/

»

Regionaltag SportReich

Verfasst von Gast am 13. September 2012 - 12:05
00.00.
Array

der TechnologieRegion Karlsruhe findet in der Bäderwelt Bretten statt. Rund um das Thema Wasser gibt es ein abwechslungsreiches Programm. Der Eintritt in die Bäderwelt ist an diesem Tag frei.

Veranstalter: Stadt Bretten, Stadtwerke Bretten, TV Bretten

Ort: Bäderwelt Bretten, Max-Planck-Str. 1

www.regionaltag2012.de

»

Sportlerehrung mit Sportgala

Verfasst von Gast am 9. Februar 2012 - 9:23
00.00.
Array

Veranstalter: Stadt Bretten

Ort: Hallensportzentrum "Im Grüner"

»

Deutsche Meisterschaften im Sitzball (Damen + Herren)

Verfasst von Gast am 8. Februar 2012 - 13:57
00.00.
Array

Ort: Hallensportzentrum "Im Grüner"

»

Deutsche Meisterschaften im Sitzball (Damen + Herren)

Verfasst von Gast am 8. Februar 2012 - 13:56
00.00.
Array

Ort: Hallensportzentrum "Im Grüner"

»

Sparkasse Kraichgau-CityCup

Verfasst von Gast am 31. Januar 2012 - 11:20
00.00.
Array

17.00 Uhr Schüler/Schülerinnen D+Minis ca. 800 m

17.30 Uhr Schüler/Schülerinnen A-C ca. 2.000 m

18.00 Uhr 5 km Lauf, AOK-Walking, AOK-Nordic Walking

19.00 Uhr 10 km Sparkasse Kraichgau-CityCup und 4 x 2,5 km Staffel

Start und Ziel ist jeweils auf der Georg-Wörner-Straße bei der Sportanlage des TV Bretten. Weitere Informationen zu Strecken u.a. unter www.citycup-bretten.de

»

Frühjahrsprüfung

Verfasst von Gast am 23. Dezember 2011 - 10:03
00.00.
Array

Veranstalter: Hundesportverein Bauerbach

Ort: Vereinsgelände

»
Inhalt abgleichen