Speed methodology
How we measure the delay between a headline and the market's reaction
This page explains, in full, how MoveSurge measures the gap between a public post or wire
headline and the market's first measured price move -- including one complete worked
example with exact timestamps, and an honest account of what this methodology does and
does not currently prove.
The short, honest version
What follows is a real, rigorously timestamped case study of a single event, not a
statistically representative sample across thousands of headlines. Any speed comparison you
see elsewhere on this site describing MoveSurge as faster than a specific competitor on a
specific event is grounded in cases like this one -- individually verified, not
automatically benchmarked at scale yet. We think that distinction matters, so we're stating
it plainly rather than letting a percentage figure imply more than the underlying evidence
currently supports.
Definitions
| Public-post timestamp | The timestamp Truth Social (or the relevant wire) attaches to the post at the moment it becomes publicly visible -- not when MoveSurge's own system ingested it. |
|---|
| First measured reaction | The first sustained, directional price move in the named instrument following the public-post timestamp, read from live tick data -- not a delayed or end-of-day close. |
|---|
| Delay | The wall-clock gap between the public-post timestamp and the first measured reaction, in seconds. |
|---|
| "Market-moving" | An event is treated as market-moving for this methodology when a named, liquid instrument shows a clear, sustained directional move within the minutes following the post -- not every post that could theoretically be relevant. |
|---|
A full worked example
On Mar 23, 2026, the trump/iran de-escalation post
crossed publicly on Truth Social. Here is the complete, exact timeline MoveSurge captured:
Fast is only useful when you catch the story
Wide coverage. Fast delivery. Clear answers.
Seven market specialists watch global markets, U.S. stocks of every size, central banks, economic data, politics, oil, gold, and more. The team brings market experience dating back to 2006. They explain what matters in plain words and get straight to the point.
Why the mix matters
Fast means little if you miss the story.
We catch it. We get it to you fast. We make it easy to understand.
MOVESURGE EXACT PUBLISH TIMESTAMP
07:05:14.720 ET
12:05:14.720 Paris
The Dow (US30) moved
07:05:15.366 ET
+0.646s
+1.89% at 1m · +3.39% at 5m · +3.17% at 10m
The Nasdaq (US100) followed
07:05:16.407 ET
+1.687s
+1.71% at 1m · +3.03% at 5m · +3.36% at 10m
Trump/Iran de-escalation post · Observed Mar 23, 2026 case. Delay is measured from the Truth Social public-post timestamp to the first sustained vertical index move. One event, not a guarantee of future latency or performance.
The running record
We are not quoting a median yet. This record holds 0
measured releases, and it takes
10 before an average says anything about the pipeline
rather than about one morning. The observations collected so far are below; the
headline number appears here once the sample is large enough to defend.
No scheduled releases have been measured yet. The first rows appear here on their own,
without anyone editing this page.
What this one case does and doesn't prove
It proves MoveSurge's pipeline is capable of capturing a public post and a named
instrument's reaction to sub-second and low-single-second precision, with exact,
independently verifiable timestamps, on at least this one occasion. It does not, on its
own, prove a general win rate against any specific competitor across all breaking news --
that would require a standing, published, repeatable benchmark comparing simultaneous
timestamped captures across multiple providers on the same events, over an extended
period.
What a fuller benchmark would need
- An explicit comparison period and a defined, non-cherry-picked set of qualifying events.
- A clear, published definition of "market-moving" applied consistently across every event in the sample.
- A named timestamp source for each competitor being compared, with a stated position on whether that timestamp reflects publication, API delivery, browser rendering, or end-user receipt -- these are meaningfully different things.
- A documented treatment for ties, edited headlines, and duplicate or re-published stories.
- Downloadable sample data so the comparison can be independently checked, not just quoted.
- An explicit statement of limitations and any conflicts of interest in how the comparison was run.
Have today One fully documented, timestamp-verified case (above), plus the running record of scheduled releases further up this page, which is written automatically and keeps its losses.
Still missing A head-to-head against other providers on the same unscheduled headlines. That needs simultaneous timestamped capture from each provider, which we do not have, so nothing on this page claims it.