Netzbetreiber kündigt Bilanzkreisvertrag mit Care Energy AG

Seit dem 29. Juni 2016 werden Kunden des Stromanbieters „Care Energy AG“ im Netzgebiet der ENWG Energienetze Weimar GmbH & Co. KG durch die Stadtwerke Weimar Stadtversorgungs-GmbH im Rahmen der Ersatzversorgung mit Strom beliefert.

„Hintergrund ist der beendete Bilanzkreisvertrag zwischen Care Energy und 50 Herz“, erklärt die Prokuristen der ENWG, Katharina Fiedler. „Der Lieferantenrahmenvertrag zwischen Care Energy und uns, als Netzbetreiber, wurde zum 28.06.2016 fristlos gekündigt“, sagt Katharina Fiedler weiter.

Grund zur Beunruhigung gibt es nicht, versichert der Geschäftsführer der Stadtwerke Weimar, Jörn Otto: „Die betroffenen Kunden müssen keinen Lieferstopp befürchten. Die Stadtwerke als Grundversorger im Netzgebiet der ENWG Energienetze Weimar haben automatisch die Versorgung übernommen.“

Die Stadtwerke Weimar informieren alle betroffenen Kunden schriftlich. Angesichts möglicher Mehrkosten raten die Stadtwerke, umgehend die Zählerstände abzulesen, zu notieren und zu melden. Eventuelle Ansprüche müssten aber bei Care Energy geltend gemacht werden.

Natürlich können die betroffenen Kunden in die günstigeren WeimarStrom und WeimarGas-Produkte wechseln. Für alle Fragen rund um die Energieversorgung können sie sich gern in unserem Kundenzentrum, Industriestraße 14 persönlich beraten lassen.

Name	Zweck	Ablauf	Typ	Anbieter
CookieConsent	Speichert Ihre Einwilligung zur Verwendung von Cookies.	1 Jahr	HTML	Website
fe_typo_user	Ordnet Ihren Browser einer Session auf dem Server zu. Dies beeinflusst nur die Inhalte, die Sie sehen und wird von uns nicht ausgewertet oder weiterverarbeitet.	Session	HTTP	Website

Name	Zweck	Ablauf	Typ	Anbieter
_ga	Wird verwendet, um Benutzer zu unterscheiden.	2 Jahre	HTML	Google
_gat	Wird zum Drosseln der Anfragerate verwendet.	1 Tag	HTML	Google
_gid	Wird verwendet, um Benutzer zu unterscheiden.	1 Tag	HTML	Google
_ga_--container-id--	Speichert den aktuellen Sessionstatus.	2 Jahre	HTML	Google
_gac_--property-id--	Enthält Informationen zu Kampagnen für den Benutzer. Wenn Sie Ihr Google Analytics- und Ihr Google Ads Konto verknüpft haben, werden Elemente zur Effizienzmessung dieses Cookie lesen, sofern Sie dies nicht deaktivieren.	3 Monate	HTML	Google
hjSiteLang	This cookie is set when a page that supports multiple languages on hotjar.com is visited. This allows us to always load the content in the preferred language when available.	1 Jahr	HTML	Hotjar
_hjptid	This cookie is set for logged in users of Hotjar who have Admin Team Member permissions. It is used during pricing experiments to show the Admin consistent pricing across the site.	1 Session	HTML	Hotjar
_hjOptOut	Hotjar Opt-Out setting. More information can be found on our Do Not Track Page	1 4 months	HTML	Hotjar
X-Access-Key	This cookie keeps your website session alive.	1 Session	HTML	Hotjar
_hjClosedSurveyInvites	Hotjar cookie that is set once a user interacts with an External Link Survey invitation modal. It is used to ensure that the same invite does not reappear if it has already been shown.	1 Jahr	Boolean true/false	Hotjar
_hjDonePolls	Hotjar cookie that is set once a user completes a survey using the On-site Survey widget. It is used to ensure that the same survey does not reappear if it has already been filled in.	1 Jahr	Boolean true/false	Hotjar
_hjMinimizedPolls	Hotjar cookie that is set once a user minimizes an On-site Survey widget. It is used to ensure that the widget stays minimized when the user navigates through your site.	1 Jahr	Boolean true/false	Hotjar
_hjShownFeedbackMessage	Hotjar cookie that is set when a user minimizes or completes Incoming Feedback. This is done so that the Incoming Feedback will load as minimized immediately if the user navigates to another page where it is set to show.	1 Jahr	Boolean true/false	Hotjar
_hjsessionTooLarge	Causes Hotjar to stop collecting data if a session becomes too large. This is determined automatically by a signal from the WebSocket server if the session size exceeds the limit.	1 Session	Boolean true/false	Hotjar
_hjid	Hotjar cookie that is set when the customer first lands on a page with the Hotjar script. It is used to persist the Hotjar User ID, unique to that site on the browser. This ensures that behavior in subsequent visits to the same site will be attributed to the same user ID.	1 Jahr	UUID	Hotjar
_hjRecordingLastActivity	This should be found in Session storage (as opposed to cookies). This gets updated when a user recording starts and when data is sent through the WebSocket (the user performs an action that Hotjar records).	1 Session	Numerical Value (Timestamp)	Hotjar
_hjTLDTest	When the Hotjar script executes we try to determine the most generic cookie path we should use, instead of the page hostname. This is done so that cookies can be shared across subdomains (where applicable). To determine this, we try to store the _hjTLDTest cookie for different URL substring alternatives until it fails. After this check, the cookie is removed.	1 Session	Boolean true/false	Hotjar
_hjUserAttributesHash	User Attributes sent through the Hotjar Identify API are cached for the duration of the session in order to know when an attribute has changed and needs to be updated.	1 Session	Hash	Hotjar
_hjCachedUserAttributes	This cookie stores User Attributes which are sent through the Hotjar Identify API, whenever the user is not in the sample. These attributes will only be saved if the user interacts with a Hotjar Feedback tool.	1 Session	JSON	Hotjar
_hjLocalStorageTest	This cookie is used to check if the Hotjar Tracking Script can use local storage. If it can, a value of 1 is set in this cookie. The data stored in_hjLocalStorageTest has no expiration time, but it is deleted almost immediately after it is created.	1 Under 100ms	Boolean true/false	Hotjar
_hjIncludedInPageviewSample	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's pageview limit.	1 30 minutes	Boolean true/false	Hotjar
_hjIncludedInsessionSample	This cookie is set to let Hotjar know whether that user is included in the data sampling defined by your site's daily session limit.	1 30 minutes	Boolean true/false	Hotjar
_hjAbsolutesessionInProgress	This cookie is used to detect the first pageview session of a user. This is a True/False flag set by the cookie.	1 30 minutes	Boolean true/false	Hotjar
_hjFirstSeen	This is set to identify a new user’s first session. It stores a true/false value, indicating whether this was the first time Hotjar saw this user. It is used by Recording filters to identify new user sessions.	1 Session	Boolean true/false	Hotjar
_hjViewportId	This stores information about the user viewport such as size and dimensions.	1 Session	UUID	Hotjar
_hjRecordingEnabled	This is added when a Recording starts and is read when the recording module is initialized to see if the user is already in a recording in a particular session.	1 Session	Boolean true/false	Hotjar

Netzbetreiber kündigt Bilanzkreisvertrag mit Care Energy AG

Unsere Unternehmen – Nachhaltig & Umweltbewusst

Photovoltaik-Anlagen

E-mobilität

Klima und Umwelt

Suche

Bereich Stadtwerke

Bereich Stadtwirtschaft

Kundenservice