USDJPY-OBS-001 TOKYO JST --:--:-- UTC --:--:-- STATUS: 28 series live Updates on LINE (Japanese)

日本語 / English

METATRADER

So that a backtest cannot read the future.

CFTC positioning refers to Tuesday. It is published Friday at 15:30 ET. Index a backtest by observation date and the strategy tester reads Friday's number on Tuesday. The result will look good. It is not true.

This feed is ordered by publisher_release_at — the moment the market could first know a number. A source that only keeps observation dates cannot offer this.

The three-day gap, concretely

LOOK-AHEAD
FieldValue
Observation date2026-08-18
Published2026-08-21T15:30:00-04:00
Gap3 days
Value-52893
Attach that number to the observation date and a tester sees it three days early. Every historical CSV in this feed is ordered by release time instead, with the observation date carried alongside so you can check the difference yourself.

Indicator

DOWNLOAD

Source included, CC BY 4.0. Both versions behave identically.

FilePlatformRequiresSize
YendollerPanel.mq4MT4(MQL4)Terminal build 600 or later (uses WebRequest, StringSplit, input)11,828B
YendollerPanel.mq5MT5(MQL5)No constraint10,991B
It emits no trading signals. No arrows, no colour coding for strength, no buy or sell verdict. It shows the number a publisher published and when they published it. Scheduled-release lines are all drawn in the same colour and weight: we do not rank events by importance.
You must whitelist https://yendoller.com under Tools → Options → Expert Advisors. Without it MT4 returns error 4060 and MT5 returns 4014; the indicator prints the fix to the log. The MT4 build needs terminal build 600 or later. We cannot compile MQL here, so please compile in MetaEditor yourself — syntax and API use are checked statically.

Feed files

FILES

Flat formats readable with StringSplit alone. MQL has no JSON parser, and asking every user to write one is a bug source.

FileContents
latest.txtCurrent values, KEY=VALUE
events.txtUpcoming scheduled releases (9 entries)
cftc.legacy.jpy.noncomm_net.csvHistorical, ordered by release time — 400 rows (value)
cftc.tff.jpy.lev_money_net.csvHistorical, ordered by release time — 400 rows (value)
drv.gap.jp_us.csvHistorical, ordered by release time — 233 rows (gap2y)
drv.hedge_cost.jpy.rate_component.csvHistorical, ordered by release time — 1262 rows (value)
drv.theoretical_swap.csvHistorical, ordered by release time — 500 rows (usdjpy)
drv.usdjpy.decomposition.csvHistorical, ordered by release time — 120 rows (usdjpy)
drv.usdjpy.rv.csvHistorical, ordered by release time — 260 rows (rv20)
obs.usdjpy.close.daily.csvHistorical, ordered by release time — 260 rows (value)
rate.us.ust.10y.csvHistorical, ordered by release time — 249 rows (value)
rate.us.ust.2y.csvHistorical, ordered by release time — 249 rows (value)

Historical CSVs carry release_epoch, release_utc, value, observation_date, status and record_id. Rows are ordered by release time, not observation date.

NO_SIGNALS=1 and NO_FORECAST=1 appear in latest.txt — a machine-readable statement that this feed contains no signals and no forecasts.

Price

FREE

Free. No registration, no authentication. Article 38 of our charter commits us to keeping the basic data and API free; a paid tier, if it ever launches, would cover support and uptime guarantees, not the data.

Bug reports: report form (Japanese) or info@yendoller.com. A contact address is optional — you may report without expecting a reply.

Get releases and corrections on LINEJapanese only. No forecasts, no signals.
Subscribe