German Grid Congestion Monitor (Redispatch)
Pricing
from $1.00 / 1,000 redispatch massnahmes
Track Germany's official redispatch measures: day-level Netzengpass data with MW/MWh, reason, direction and transmission operator, plus a congestion status per operator and month that excludes commissioning tests. Official BNetzA source, from $0.001/measure (PPE).
Only measures ordered by these Übertragungsnetzbetreiber (transmission system operators): "50Hertz", "Amprion", "TenneT DE", "TransnetBW". Case is ignored. Empty = all four.
Only measures with this official reason. Valid values: "Strombedingter Redispatch" (congestion-related redispatch), "Strombedingter Redispatch kurativ", "Strom- und Spannungsbedingter RD", "Spannungsbedingter Redispatch", "Probefahrt" (commissioning test), "Strombedingter Countertrade DE-DK1", "Strombedingter Countertrade DE-DK2". Empty = all.
"Wirkleistungseinspeisung reduzieren" = output cut (the congestion trigger) or "Wirkleistungseinspeisung erhöhen" = the offsetting measure. Empty = both.
Only measures on plants of these energy carriers: "Konventionell", "Erneuerbar", "Sonstiges". Empty = all.
Free-text filter on the official plant name, e.g. "Mehrum", "Börse" or "Dörpen". Case is ignored, and German umlauts are folded to their ASCII convention: "Doerpen" finds "Dörpen-West", and "dörpen" does too. ("Dorpen" does not — plain "o" and "oe" are kept distinct.)
If true, drop rows whose reason is not a grid-congestion measure. In practice this removes "Probefahrt" (commissioning tests of reserve plants), which the source publishes in the same table and which made up about 5.9% of 2026 energy. The monthly congestion status and the summary already exclude these rows regardless of this setting; this field only filters the delivered individual measures.
Only measures whose maximum capacity is at least this many MW.
Only measures whose total energy is at least this many MWh. Useful to strip routine small measures when you only want the significant congestion events.
Cap on how many individual measure records are delivered per run (whole number, at least 1). Default 500; set a very high value for the complete set. Without a cap, the first run of a year set would deliver roughly 17,000 records and a later full-snapshot run would bill for all of them. With a cap the most significant measures come first (highest total energy, then highest peak capacity, then most recent). Records that fall outside the cap are NOT added to the change-detection baseline, so a following run detects them again and delivers the next batch: nothing is silently lost, you just receive the set in batches. The free summary always covers the full filtered set and reports abgeschnitten together with anzahlVorAbschneidung and anzahlGeliefert. The cap also applies to a first run, but a first run never charges.
Which measures to deliver. "aktuelles_jahr" (default) = the year-to-date set published by the source. "letzte_30_tage" and "letzte_7_tage" = only measures that overlap the last 30 or 7 days before the run. The filtering is done in the Actor, because the source ignores the date fields of its own download form.
If true (default), the Actor also delivers one aggregated profile per transmission operator and calendar month. Each profile carries the total energy, the congestion-relevant energy (excluding commissioning tests), the MWh per covered calendar day, the measure and plant counts, the direction split, the main reason and two derived congestion statuses: an absolute one on the month total and a daily-rate one that stays comparable for a partial current month.
If true (default), only measures that are new or changed since the previous run are delivered and charged. If false, every run delivers the full filtered set (subject to maxMassnahmen), but only new/changed measures are still charged as a congestion alert. Uses a persistent baseline in a named key-value store that all runs of this Actor share — including the pre-publication validation run — so the baseline is actor-wide, not per user. Only a baseline that does not exist yet makes the entire filtered set count as new; the default true setting therefore delivers nothing when the baseline already covers the filtered set.
