Transmission Lines

Data on capacity, scheduled trade, actual exchange and congestion income.

The TSOs decide how much capacity is to be transferred, and the capacity for the coming day is published at Nord Pool Spot every day before 10:00.

Scheduled trade on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation. The physical exchange is the actual measured exchange of electricity. Negative values indicate export of electricity out of the area to the connected area, and positive values indicate import.

Congestion rent is calculated as the difference in spot prices between the two price areas multiplied by the estimated exchange between the two areas concerned. The international connections to Norway and Sweden are completely at the disposal of NordPool Spot and in return the TSOs receive the congestion rent. In NORDEL (Denmark, Norway, Sweden, Finland, Iceland) the congestion rent is distributed according to a scale agreed upon. With regard to the KONTEK interconnection the congestion rent is paid to Energinet.dk, Vattenfall Europe Transmission and Vattenfall AB (Vattenfall’s trading company in Sweden) according to a scale agreed upon.

The interconnection between Western Denmark and Germany is at the disposal of the market at annual, monthly and daily auctions at which payment for utilization of the interconnection - and thereby the congestion rent - is calculated on the basis of demand and supply. The congestion rent is equally divided between Energinet.dk and E.ON Netz.


Hour UTC

Comment

Please note that the format shown in the example applies to data download as JSON, XML or fetched through the API and is in accordance with the ISO 8601 standard. The format is slightly different when it is shown on screen or downloaded manually as CSV or XLSX. This is mainly due to readability and consideration for Excel users.

In preview (in the GUI) all timestamps are shown as (display convention) YYYY-MM-DD hh:mmZ e.g. 2017-07-14 08:00Z. The Z will remind viewers that this is UTC.

In download (CSV and XLSX) the date time are exported as YYYY-MM-DD hh:mm e.g. 2017-07-14 08:00. That is without the \u201cT\u201d and the \u201cZ\u201d and the seconds. Excel will recognize it as date-time. The user must remember the convention about time zones.

In download (JSON and XML) the full format is used YYYY-MM-DDThh:mmZ e.g. 2017-07-14T08:00Z.

Description

A date and time (interval), shown in UTC time zone, where the values are valid. 00:00 o\u2019clock is the first hour of a given day interval 00:00 - 00:59 and 01:00 covers the second hour (interval) of the day and so forth. Please note: The naming is based on the length of the interval of the finest grain of the resolution.

Title

Hour UTC

Property constraint
Format
Name

HourUTC

Validation rules

Always full hours, i.e. minutes are 00

Type

datetime

Example

2017-07-14T08:00Z

Unit
Size

17

Hour DK

Comment

On one normal day there will be 24 intervals.

When daylight saving times shifts there will be either 23 or 25 intervals.

Please note that the format shown in the example applies to data download as JSON, XML or fetched through the API and is in accordance with the ISO 8601 standard. The format is slightly different when it is shown on screen or downloaded manually as CSV or XLSX. This is mainly due to readability and consideration for Excel users.

In preview (in the GUI) all timestamps are shown as (display convention) YYYY-MM-DD hh:mm e.g. 2017-07-14 08:00. Please note that is no time zone indicator, showning that this is local (Danish) time.

In download (CSV and XLSX) the date time are exported as YYYY-MM-DD hh:mm e.g. 2017-07-14 08:00. That is without the \u201cT\u201d and the seconds. Excel will recognize it as date-time. The user must remember that this is local (Danish) time.

In download (JSON and XML) the format used is YYYY-MM-DDThh:mm e.g. 2017-07-14T08:00.

Description

A date and time (interval), shown in Danish time zone, where the values are valid. 00:00 o\u2019clock is the first hour of a given day, interval 00:00 - 00:59, and 01:00 covers the second hour period (interval) of the day and so forth.

Title

Hour DK

Property constraint
Format
Name

HourDK

Validation rules

Always full hours, i.e. minutes are 00

Type

datetime

Example

2017-07-14T08:00

Unit
Size

17

Price area

Comment

If price area is \u201cDK\u201d, the data covers all Denmark.

Description

Same as bidding zone. Denmark is divided in two price areas, or bidding zones, divided by the Great Belt. DK1 is west of the Great Belt and DK2 is east of the Great Belt.

Title

Price area

Property constraint
Format

DK1 | DK2

Name

PriceArea

Validation rules

DK1 or DK2

Type

string

Example

DK1

Unit
Size

3

Connected area

Comment

DK1 is the Jutland and Fyen and DK2 is Zealand and islands. DK1 is connected to Norway (Oslo), Sweden (SE3) and Germany (EPEX) DK2 to Sweden (SE4) and Germany (EPEX)

Description

The destination area of the connection.

Title

Connected area

Property constraint
Format

DK1 | DK2 | SE3 | SE4 | NO2 | DE

Name

ConnectedArea

Validation rules

One of the following values DK1, DK2. SE3, SE4, NO2, DE

Type

string

Example

DK1

Unit

text

Size

8

Import capacity

Comment
Description

Import capacity from connected area to the area. The TSOs decide how much import capacity is to be transferred, and the capacity for the coming day is published at Nord Pool Spot every day before 10:00.

Title

Import capacity

Property constraint
Format

([0-9]*[,])[0-9]

Name

ImportCapacity

Validation rules

=0

Type

number

Example

184.3

Unit

MWh per hour

Size

9.1

Export capacity

Comment
Description

Export capacity from area to the connected area. The TSOs decide how much export capacity is to be transferred, and the capacity for the coming day is published at Nord Pool Spot every day before 10:00.

Title

Export capacity

Property constraint
Format

([0-9]*[,])[0-9]

Name

ExportCapacity

Validation rules
Type

number

Example

184.3

Unit

MWh per hour

Size

9.1

Scheduled exchange day ahead

Comment

Positive values are import from connected area to the area. Negative values are eksport from area to connected area.

Description

Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation

Title

Scheduled exchange day ahead

Property constraint
Format

([0-9]*[,])[0-9]

Name

ScheduledExchangeDayAhead

Validation rules
Type

number

Example

184.3

Unit

MWh per hour

Size

9.1

Scheduled exchange intraday

Comment

Positive values are import from connected area to the area. Negative values are eksport from area to connected area.

Description

Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation

Title

Scheduled exchange intraday

Property constraint
Format

([0-9]*[,])[0-9]

Name

ScheduledExchangeIntraday

Validation rules
Type

number

Example

184.3

Unit

MWh per hour

Size

9.1

Physical exchange non-validated

Comment

Positive values are import from connected area to the area. Negative values are eksport from area to connected area.

Description

Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation

Title

Physical exchange non-validated

Property constraint
Format

([0-9]*[,])[0-9]

Name

PhysicalExchangeNonvalidated

Validation rules
Type

number

Example

184.3

Unit

MWh per hour

Size

9.1

Physical exchange settlement

Comment

Positive values are import from connected area to the area. Negative values are eksport from area to connected area.

Description

Scheduled exchange on the transmission lines is the flow of electricity from areas of surplus to areas of deficit resulting from the Nord Pool Spots price calculation

Title

Physical exchange settlement

Property constraint
Format

([0-9]*[,])[0-9]

Name

PhysicalExchangeSettlement

Validation rules
Type

number

Example

184.3

Unit

MWh per hour

Size

9.1

Congestion income (DKK)

Comment

([0-9]*[,])[0-9][0-9]

Description

9.2

Title

Congestion income (DKK)

Property constraint
Format

Congestion income from connection between price areas.

Name

CongestionIncomeDKK

Validation rules
Type

number

Example

Congestion income is calculated as the difference in spot prices between the two price areas multiplied by the estimated exchange between the two areas concerned.

Unit

DKK per hour

Size

9.2

Home price (DKK)

Comment
Description

Price in the home price area

Title

Home price (DKK)

Property constraint
Format

([0-9]*[,])[0-9][0-9]

Name

HomePriceDKK

Validation rules
Type

number

Example

543,45

Unit

DKK per hour

Size

9.2

Connected price (DKK)

Comment
Description

Price in the connected area

Title

Connected price (DKK)

Property constraint
Format

([0-9]*[,])[0-9][0-9]

Name

ConnectedPriceDKK

Validation rules
Type

number

Example

300.0

Unit

DKK per hour

Size

9.2

Congestion income (EUR)

Comment

Congestion income is calculated as the difference in spot prices between the two price areas multiplied by the estimated exchange between the two areas concerned.

Description

Congestion income from connection between price areas.

Title

Congestion income (EUR)

Property constraint
Format

([0-9]*[,])[0-9][0-9]

Name

CongestionIncomeEUR

Validation rules
Type

number

Example

300.0

Unit

EUR per hour

Size

9.2

Home price (EUR)

Comment
Description

Price in the home price area

Title

Home price (EUR)

Property constraint
Format

([0-9]*[,])[0-9][0-9]

Name

HomePriceEUR

Validation rules
Type

number

Example

543,45

Unit

EUR per hour

Size

9.2

Connected price (EUR)

Comment
Description

Price in the connected area

Title

Connected price (EUR)

Property constraint
Format

([0-9]*[,])[0-9][0-9]

Name

ConnectedPriceEUR

Validation rules
Type

number

Example

300.0

Unit

EUR per hour

Size

9.2