summary: the numbers in a video, screenshot, or stream were accurate when they were captured — the dataset has moved forward since, and the settings the host had up probably aren't yours. here's why it happens, the five settings to match, and how close you can realistically get.
why the numbers don't match
this is one of the most common questions we get. you're watching an edgeful video or looking at a screenshot someone shared, and the percentages on your screen don't match. that's expected — it's not a bug, and your data isn't wrong.
edgeful reports are calculated from historical market data, and that data updates every single day. a video recorded three months ago was showing the data as of that date. since then dozens of new trading days have been added, and older days may have rolled off depending on the lookback. so the numbers shift — sometimes a little, sometimes more, depending on how the market has behaved since.
but time isn't the only reason. five settings control what a report shows you, and if any one of them differs from what the host had up, the output differs too.
where you'll see this
it applies anywhere you see edgeful data outside your own account:
YouTube videos — recorded at a point in time with specific settings
X posts and Discord screenshots — captured at the moment of posting, often with the poster's own customization
webinars and live streams — even "live" content shows that day's data
blog posts and articles — same as videos, pulled at a point in time
in every case the content was accurate when it was created. the data has simply moved forward.
the five settings that control what you see
every report runs on the same core settings in the left sidebar. check them in this order:
ticker. the simplest one, and worth ruling out first. NQ and ES are both index futures but they're different data — a video on NQ will never match your ES screen.
session. the session doesn't just filter which slice you see — it changes what the report is measuring. NY session and London session data on the same report and the same ticker can look completely different, and they should. they're two different measurements, not two views of one.
subreport. the dropdown directly below the report selector slices the same dataset by a different dimension. standard is the base view, by weekday breaks it out by day of week, by levels shows extension targets. a video on by-levels against your standard view isn't a mismatch — it's two different cuts. see subreports.
customization. this is the one that catches people most. inside the customize panel there are report-specific parameters that change how the number is calculated. the ORB report has a break type setting — first break vs all breaks — and the two produce very different numbers on the by-levels subreport. the IB report has its own window options, and gap fill has an adjustable fill threshold.
the part worth knowing: customizations are saved per report, on your account. if you changed one months ago it's still set that way, and it will quietly not match a video showing defaults. when a number looks off and everything else lines up, open customize before anything else.
date range. the biggest one. a video showing "6 months" of data in January 2026 was looking at July through January. select "6 months" on the same report today and you're looking at an entirely different six-month window. even with all four settings above matched perfectly, the date range alone will move the number — because the market keeps trading and the dataset keeps growing.
for a full walkthrough of every control on the report page, see navigating and customizing reports.
how close can you actually get
match those five in that order and the numbers should converge. one caveat that no amount of matching fixes: if the content is more than a day old, they won't be identical, because new market data has been added since. the closer in time you are to when it was recorded, the closer you'll get.
if all five are matched and the numbers still disagree, the remaining causes aren't video-specific — timezone, session windows, contract rollovers, and wick vs close. work the checklist in why doesn't my number match?
a note for forex
if you trade forex there's a cause that has nothing to do with settings or timing — the feed itself. edgeful's FX data comes from a different provider than TradingView's default forex feed, so the spread and the exact high, low, and open of a candle can differ slightly. that's a feed difference, not an error on either side. more on it in why your edgeful data doesn't match TradingView.
futures, stocks, and ETFs don't run into this the same way — forex is the one to keep in mind.
this is actually a good thing
numbers changing over time means the data is live. you're not looking at a static table, you're looking at a rolling dataset that updates with every new trading day. a stat that has slipped a couple of points since you last looked isn't wrong — it's telling you the market has shifted slightly. if it's moved up instead, the edge has strengthened.
that's why comparing date ranges matters. check the same report across 1 year, 6 months, and 3 months — consistent across all three means the pattern is stable; a short-term number that's dropped off may mean the setup is weakening. the data tells you either way.