Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Fixed Income Futures
Fixed Income Options
STIR Futures & Options
Credit Index Futures
Financing of Futures CTDs
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
STOXX
MSCI
FTSE
DAX
Mini-DAX
Micro Product Suite
Daily Options
Index Total Return Futures
ESG Index Derivatives
Country Indexes
KOSPI
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Product Overview
Daily Options
Three-Month Euro STR Futures
Credit Index Futures
EURO STOXX 50® Index Futures
Exchange Participants
Market Maker Futures
Market Maker Options
ISV & service provider
3rd Party Information Provider
Market data vendors
Brokers
Multilateral and Brokerage Functionality
Block Trades
Delta TAM
T7 Entry Service via e-mail
Vola Trades
Additional contract versions
Exchange for Physicals
Trade at Index Close
Exchange for Swaps
Non-disclosure facility
Market statistics (online)
Trading statistics
Monthly statistics
Eurex Repo statistics
Snapshot summary report
Product parameter files
T7 Entry Service parameters
EFS Trades
EFP-Fin Trades
EFP-Index Trades
MiFID2 Commodity Derivatives Instruments
Total Return Futures conversion parameters
Product and Price Report
Variance Futures conversion parameters
Suspension Reports
Position Limits
RDF Files
Prices Rolling Spot Future
Notified Bonds | Deliverable Bonds and Conversion Factors
Risk parameters and initial margins
Securities margin groups and classes
Haircut and adjusted exchange rate
Cross-Project-Calendar
Readiness for projects
T7 Release 13.1
T7 Release 13.0
T7 Release 12.1
T7 Release 12.0
Member Section Releases
Simulation calendar
Archive
Direct market access from the U.S.
Eligible options under SEC class No-Action Relief
Eligible foreign security futures products under 2009 SEC Order and Commodity Exchange Act
U.S. Introducing Broker direct Eurex access
Newsletter Subscription
Circulars & Newsflashes Subscription
Corporate Action Information Subscription
Circulars & Newsflashes
Derivatives Forum
Eurex has recalibrated the Order-to-Trade Ratio (OTR) with effect from 1 January 2021. Main changes compared to the OTR regime until December 2020 are the newly calibrated parameters as well as the provision of intraday periods.
The limits for the volume-based OTR are set on the ratio between volume of all order-entries (ordered volume) to the trading volume per product and per day generated by orders and quotes sent by the participants to T7. The limits for the transaction-based OTR are set on the ratio between number of all order entries (number of orders) to the number of trades per product and per day generated by orders and quotes sent by the participants to T7. For the calculation of the ordered volume (respectively the number of orders), all types of orders and/or quotes are considered. This includes any/all of the following: add, modify and delete. For the calculation of the traded volume (number of trades), all executions are taken into account. Please note, the aforementioned metrics are calculated per trading day, product and per participant.
The limits are defined based on the product type. For some products with a different behaviour, the limits are modified by a product specific factor. In case a participant fulfilled the Minimum Quotation Requirements, the limits will be increased considering the quotation performance.
At the end of a day, if the value of an OTR for a particular product for a particular participant is greater than a pre-defined limit, such instance is considered a violation. A violation may trigger sanctions against the participant.
The TR100 report is published on a daily basis. Intraday versions are available as well. With the intraday reports, Participants have access to preliminary values of the OTRs as well as the respective limits during the day. The intraday versions of the report are published every 30 minutes, starting at 1:30 CET and ending at 21:30 CET (intraday versions of OTR reports for T7 FX are published from 0:30 to 22:30 CET). The final conclusion on whether the OTR is violated can be drawn only at the end of a day.
The volume-based OTR is calculated using the following equation:
OTR vol = [ ordered volume ] / [ traded volume ] - 1
The ordered volume is the sum of:
A modify of an order or quote is treated as a "delete" followed by an "add". Thus, the original order and the new order will both be counted towards the ordered volume. This process applies regardless of which attribute of the order and/or quote is changed. An IOC order is treated like an order submission, while the unexecuted portion will be treated like an order deletion.
If an order or a quote is fully or partially deleted by the Self-Match Prevention (SMP) functionality then the ordered volume is increased both on the buy- and the sell-side only by the number of the deleted contracts.
The traded volume is the executed volume in the order book. If the traded volume is smaller than the volume-based minimum value, it is replaced with the volume-based minimum value.
The limit of the volume-based OTR considers the product type, the product. For participants fulfilling the minimum quotation requirements we apply higher and dynamic limits. The dynamic limits are depending on the quote performance (i.e. number of instruments and time with quotes in relation to the minimum requirements), the spread quality, the average quote size, as well as quotation during stressed market conditions.
Please find below a concept paper describing the calculation (including an example) in detail.
The transaction-based OTR is calculated using the following equation:
OTR count = [ number of orders ] / [ number of trades ] - 1
The number of orders is the sum of:
A modify of an order or quote is treated as a "delete" followed by an "add". Thus, the original order and the new order will both be counted towards the number of orders. This process applies regardless of which attribute of the order and/or quote is changed. An IOC order is treated like an order submission, while the unexecuted portion will be treated like an order deletion.
If an order or a quote is fully or partially deleted by the Self-Match Prevention (SMP) functionality then the number of orders is increased both on the buy- and the sell-side only by the number of involved orders.
The number of trades is the number of executions in the order book. If the number of trades is smaller than the transaction-based minimum value, it is replaced with the transaction-based minimum value.
The limit of the transaction-based OTR considers the product type, and the product. For participants fulfilling the minimum quotation requirements we apply higher and dynamic limits. The dynamic limits are depending on the quote performance (i.e. number of instruments and time with quotes in relation to the minimum requirements), the spread quality as well as quotation during stressed market conditions.
Please find below a concept paper describing the calculation (including an example) in detail.
The following tables show the parameters used to calculate the volume based OTR.
Please note: The limit is based on the product type of the product.
If a product is not included in the table, i.e. has no product factor assigned, the default value of 1.00 is applied.
The following tables show the parameters used to calculate the transaction based OTR.
Please note: The limit is based on the product type of the product.
If a product is not included in the table, i.e. has no product factor assigned, the default value of 1.00 is applied.
The following reports will be available for the Participants on the Common Report Engine:
Under further information you can find a concept paper describing the calculation (including an example) in detail.
Market Status ⓘ
XEUR
The market status window is an indication regarding the current technical availability of the trading system. It indicates whether news board messages regarding current technical issues of the trading system have been published or will be published shortly.
Please find further information about incident handling in the Emergency Playbook published on the Eurex webpage under Support --> Emergencies and safeguards. Detailed information about incident communication, market re-opening procedures and best practices for order and trade reconciliation can be found in the chapters 4.2, 4.3 and 4.5, respectively. Concrete information for the respective incident will be published during the incident via newsboard message.
We strongly recommend not to take any decisions based on the indications in the market status window but to always check the production news board for comprehensive information on an incident.
An instant update of the Market Status requires an enabled up-to date Java™ version within the browser.
Name | Provider / Domain | Gültig bis | Beschreibung |
---|---|---|---|
CM_SESSIONID | eurex.com | Session | This cookie is neccessary for the CAE connection. |
JSESSIONID | www.eurex.com | Session | General purpose platform session cookie, used by sites written in JSP. Usually used to maintain an anonymous user session by the server. |
[abcdef0123456789]{32} | analytics.deutsche-boerse.com | Session | Necessary for the operation of the site. |
mdg2sessionid | eurex-api.factsetdigitalsolutions.com | Session | This cookie is necessary for visualization of charts. |
ApplicationGatewayAffinityCORS | analytics.deutsche-boerse.com | Session | This cookie is necessary for the backend connection with the server. |
ApplicationGatewayAffinity | eurex.com | Session | This cookie is necessary for the backend connection with the server. |
ApplicationGatewayAffinityCORS | eurex.com | Session | This cookie is necessary for the backend connection with the server. |
CookieScriptConsent | .eurex.com | 1 year | This cookie is used by Cookie-Script.com service to remember visitor cookie consent preferences. It is necessary for Cookie-Script.com cookie banner to work properly. |
Name | Provider / Domain | Gültig bis | Beschreibung |
---|---|---|---|
_pk_id.7.931a | www.eurex.com | 1 year | This cookie name is associated with the Piwik open source web analytics platform. It is used to help website owners track visitor behaviour and measure site performance. It is a pattern type cookie, where the prefix _pk_id is followed by a short series of numbers and letters, which is believed to be a reference code for the domain setting the cookie. |
_pk_ses.7.931a | www.eurex.com | 30 minutes | This cookie name is associated with the Piwik open source web analytics platform. It is used to help website owners track visitor behaviour and measure site performance. It is a pattern type cookie, where the prefix _pk_ses is followed by a short series of numbers and letters, which is believed to be a reference code for the domain setting the cookie. |
_pk_id.7.d059 | www.eurex.com | 1 year | This cookie name is associated with the Piwik open source web analytics platform. It is used to help website owners track visitor behaviour and measure site performance. It is a pattern type cookie, where the prefix _pk_id is followed by a short series of numbers and letters, which is believed to be a reference code for the domain setting the cookie. |
_pk_ses.7.d059 | www.eurex.com | 30 minutes | This cookie name is associated with the Piwik open source web analytics platform. It is used to help website owners track visitor behaviour and measure site performance. It is a pattern type cookie, where the prefix _pk_ses is followed by a short series of numbers and letters, which is believed to be a reference code for the domain setting the cookie. |
Name | Provider / Domain | Gültig bis | Beschreibung |
---|---|---|---|
CONSENT | .youtube.com | 1 year | This cookie carries out information about how the end user uses the website and any advertising that the end user may have seen before visiting the said website. |
VISITOR_INFO1_LIVE | .youtube.com | 6 months | This is a cookie that YouTube sets that measures your bandwidth to determine whether you get the new player interface or the old. |
YSC | .youtube.com | Session | This cookie is set by the YouTube video service on pages with embedded YouTube video. |