If your phone in Accra reads 09:15 while an active MT5 quote reads 11:15, the observed server offset is two hours ahead of Ghana for that instant. The matching chart time for a 09:15 GMT event would be 11:15 server time if the offset is still the same. Changing the phone’s timezone cannot establish the broker’s bar boundaries.
Measure the offset from a current quote, record the date and server, and subtract it when converting server timestamps to Ghana time. Compare the broker’s published time policy for historical dates. Some servers change offset seasonally while Ghana stays on GMT year-round.
Observe the offset on an active market
Use a liquid, open instrument and inspect the last quote timestamp alongside a reliable Ghana clock. Read the two within the same short interval. A server time inferred from a stale tick could appear several minutes or hours behind. MetaQuotes documents that TimeCurrent represents the last known server time associated with a received quote. MetaQuotes server time documentation
Write the comparison with dates on both sides. If 23:18 GMT on Monday corresponds to 01:18 server on Tuesday, the server is two hours ahead. Subtracting the clock faces without the dates would suggest an implausible difference. When a one-minute candle is labelled 11:15, check whether the label marks the start of the interval. A candle start is not the exact tick timestamp for every trade inside it.
Repeat the observation near a US or UK clock-change week if you rely on a recurring schedule. Do not carry an observed July offset into November without a check. US and UK changes can occur on different dates, and the broker’s server policy need not match either country’s calendar exactly. US daylight saving rules from NIST
The offsets are assumptions for the same instant. Confirm each real server on the date.
Convert in both directions
For a server ahead of GMT by two hours, convert 14:37 server to 12:37 Ghana by subtracting two. To locate a Ghana event on that server’s chart, add two. Thus 12:37 Ghana maps back to 14:37 server. Always run the reverse calculation when annotating a journal. It catches adding the offset in both directions.
If a second server is three hours ahead at the same instant, its chart time is 15:37 when the first server reads 14:37. The one-hour difference between screenshots does not mean one market reacted an hour later. Match the underlying event time and pair before making a claim about one feed leading the other.
For a historical record use a dated server rule, a paired timestamp from that day or other reliable contemporaneous evidence. Today’s phone clock comparison only verifies today’s offset. If you cannot establish a historical offset, mark the event alignment as approximate and avoid using a precise one-minute reaction in a backtest result.
Read a candle across Ghana midnight
Suppose a daily bar begins at server midnight with a plus-two offset. Its start is 22:00 Ghana time on the previous calendar date. A high recorded at 22:35 Ghana belongs to the new server day but still falls on the old Ghana date. Either grouping can be meaningful as long as your definition of “previous day” stays consistent.
An ICT study of a prior-day high depends on the chosen session boundaries. Two brokers may construct different daily highs because their daily bars enclose different hours, even if their one-minute prices agree. To compare them, extract the same Ghana or New York time interval from both feeds and calculate the maximum over that interval. Then compare the quotes at the extreme.
An apparent sweep can disappear when the reference interval changes. That finding concerns how the reference was defined. It does not by itself establish a broker error. Save the instrument, timeframe, timestamp basis and quote side alongside the screenshot to make the observation reproducible. MT5 Android chart documentation
Worked replay around a timestamp mismatch
A Ghana-based reviewer marks 13:30 GMT for a release and looks at the 13:30 candle on a plus-two server. The actual event corresponds to 15:30 server. The candle originally selected belongs to 11:30 Ghana, two hours too early. Before interpreting a pre-release sweep, move the marker and reconstruct which swings were observable before 15:30 server.
Imagine the correctly aligned synthetic replay supplies a long EUR/USD ask entry of 1.08472, bid invalidation at 1.08342 and target at 1.08732. Risk is 13 pips, reward 26 pips and gross risk to reward 1:2. The ratio does not validate the timestamp. A chart can show perfect-looking levels and still be evidence from the wrong period.
Log two records: the original candidate labelled “excluded, event alignment incorrect” and the corrected replay with its evidence. Replacing the first record silently makes it impossible to estimate how many prior results may have used the same conversion mistake.
Illustrative bracket. Entry 1.08472, stop 1.08342 and target 1.08732. Gross risk to reward is 1:2 before costs.
Create a clock key for a whole replay
Put the source clock, Ghana time and chart clock on one line before annotating any candle. A news source might say 08:30 Eastern, a phone might display 12:30 Ghana, while the server shows 15:30. These are consistent on a summer date if the server is three hours ahead of GMT. The numbers describe one instant, not a three-hour lead by the market.
| Known timestamp | Assumption | Converted result |
|---|---|---|
| 08:30 Eastern in US daylight time | New York is four hours behind GMT | 12:30 Ghana |
| 12:30 Ghana | Server is three hours ahead on the observed date | 15:30 server |
| 00:15 Tuesday on a plus-two server | Subtract two hours, keeping the date | 22:15 Monday Ghana |
| 23:45 Ghana Monday | Add two hours for that server | 01:45 Tuesday server |
Do not discard seconds when two events share a candle. An order filled at 15:30:04 and one filled at 15:30:56 belong to the same minute but may have seen different spreads. Converting both to 12:30 GMT is correct at minute resolution. It does not establish which came first unless the seconds remain available.
Understand how an offset affects a daily high
Imagine two Ghana-time observations: EUR/USD prints 1.08672 at 21:50 and 1.08814 at 22:10. A GMT calendar day includes both. A server that starts its next daily bar at 22:00 Ghana assigns them to different daily bars. If you call 1.08814 “yesterday’s high” on one chart and use it in a different server’s study, your reference may belong to a different interval.
Write the prior-day window as a half-open interval, from the start time inclusive to the next day’s start exclusive. A tick exactly at the new boundary belongs to the new interval. This convention prevents counting a boundary observation twice when calculating two adjacent daily ranges. Check how the data provider timestamps bars before applying the rule to an export.
For a study of an ICT midnight open, identify which midnight is intended. New York civil midnight, broker midnight and Ghana midnight are three different definitions. For New York midnight, the usual Ghana conversion is 05:00 during US standard time and 04:00 during US daylight time. A server daily open at another instant is a valid price but answers another question.
Build a daylight-change comparison
Take an 08:30 Eastern release on two dates straddling the US clock change. It moves from 12:30 to 13:30 Ghana as New York moves from daylight to standard time. If your broker also moves its server from GMT+3 to GMT+2 at the same transition, both may appear at 15:30 server. A stable-looking server label can thus conceal a real one-hour change on your phone.
A broker moving its server on the European schedule can create different relationships for several dates. A timetable derived from a single week cannot resolve those dates. Use dated evidence from the actual broker and the relevant country’s timezone policy. Mark uncertain weeks in your sample instead of forcing the offset that makes all pictures look alike.
When comparing a London teaching window defined in fixed Ghana time with a London local-clock market event, preserve each original definition. Converting a fixed-GMT classroom convention again for British summer time would move it away from its stated basis. Conversely, assuming a London civil-clock event stays at one GMT time throughout the year creates an error in the other direction.
Reconcile an exported deal with a phone screenshot
Use the confirmed account and full date before comparing the clock. Two phones logged into different demo servers can look nearly identical and show different stamps. Compare order identifier, symbol, quantity and actual fill price. Once the deal itself matches, convert its documented timestamp and align the event to the chart interval.
A screenshot may show the time when a screenshot was taken rather than when the candle or order occurred. A gallery timestamp is especially weak evidence of execution. Preserve the on-chart axis or history timestamp inside the image whenever possible. Write down whether you are describing the trade, the notification, the screenshot or a later annotation.
If a chart appears an entire hour out only around a clock change, a clean diagnostic is to compare one well-dated observation before the change and one after it. If both errors have the same magnitude year-round, inspect the assumed server offset. If the disagreement occurs only for daily bars, investigate their opening boundary before applying a wholesale one-hour correction to every tick.
Keep three distinct meanings of the word open
A platform can use “open” for the first quote of a candle, for the start of the instrument’s dealing session, and for the execution price of your position. These can occur at three different times. The opening value of a 15-minute candle labelled 09:00 does not establish that your order entered at 09:00 or that the entire forex market opened then.
Suppose a plus-two server’s 15-minute bar labelled 11:00 contains a deal stamped 11:08:42. In Ghana the bar starts at 09:00 and the deal occurs at 09:08:42. A journal that records the bar start as the fill time shifts the execution by more than eight minutes. It may put the trade before a news item or entry signal that was actually known by the time of execution.
For a four-hour bar, the distortion can be much larger. Use the bar start to describe interval boundaries and the deal timestamp for the actual transaction. If the only surviving evidence is the bar containing the fill, report an interval rather than inventing a precise instant.
Convert a set of records across a week boundary
A Ghana-based student studies a Sunday opening and the first Monday London session. The first quote arrives at 22:04 Ghana on Sunday. A plus-three server stamps it 01:04 Monday. A later Monday trade at 08:21 Ghana is stamped 11:21 Monday. Both server records have the same calendar date. The student’s Ghana record crosses from Sunday to Monday between them.
A query filtering the server table for Sunday alone would omit the opening quote, even though it was Sunday for the student. Convert the full Ghana interval into server boundaries before applying the data filter. For a full Ghana day, the correct selection can cover parts of two server dates. Do not filter by date first and convert the surviving records afterwards if that would discard part of the interval.
The same issue appears in monthly reports. A position closed shortly after server midnight on the first of the month can still belong to the last Ghana day of the preceding month. Your broker may correctly assign it to a new reporting period while your household cash journal assigns its local timestamp to the old month. Keep both bases and explain the boundary difference.
Test whether two apparent feed disagreements are time disagreements
Compare a distinctive sequence of several highs and lows across both feeds. If the shapes align after a consistent one-hour shift, review time labels before comparing price. If the same time-aligned candle has different highs after the timestamps match, a genuine quote-side, liquidity or aggregation difference remains possible. Do not apply an extra offset merely to make one isolated extreme coincide.
Imagine feed A prints a five-minute high of 1.08743 and feed B a high of 1.08736. The seven-point difference may matter to a marginal liquidity sweep study. First check the same pair, calendar instant, interval start, bid or ask basis and symbol specification. Only then does a residual price difference become a meaningful feed observation.
For a daily candle, rebuild the maximum within a common interval from a finer series, where available. If the reconstructed highs agree, the disagreement was likely about bar boundaries. If they still differ, review the raw observations and their completeness. A missing minute in one export is another explanation that a timezone conversion alone cannot resolve.
Keep a versioned time rule for a strategy
Write your rule in words before code or spreadsheet formulas. For example, “news events use the publisher’s Eastern date and clock, converted to Ghana; broker fills use the actual server offset for their dates; the London study uses the separately specified local session.” This rule tells a second person how to handle clocks without copying a constant from one screenshot.
If a spreadsheet stores only clock times without dates, it cannot choose the correct seasonal offset consistently. Store a full date, timezone identifier or observed fixed offset with its provenance, plus the converted instant. A Ghana-only display column can stay simple while the underlying record retains enough information for a later audit.
When a timezone rule changes or you discover a past alignment error, retain the earlier study result with its conversion version. Recalculate affected samples rather than hand-editing only those whose outcomes look surprising. Otherwise a repair intended to improve alignment can introduce hindsight bias into the strategy record.
Check a lesson recorded in another country
A video tutor may say “the candle at eight thirty” without specifying their timezone. Look for the official release, the chart’s displayed server label and a dated context before converting it. A guess based on the speaker’s location is especially weak if their platform clock follows a remote broker. Label the example unverified when those clues cannot establish the instant.
A viewer can still learn the price-pattern definition from an undated clip while avoiding a precise session claim. If the task is to classify a structural break, the missing clock may leave that classification intact. If the task is to test how often the pattern occurs at 08:30 Eastern, the missing timestamp is material. Applying the right evidence standard depends on which conclusion you intend to draw.
Construct a conversion sheet that survives a date change
Use a full timestamp for the original event and another for the converted Ghana instant. Store the named timezone or the observed broker offset in its own field. A column labelled “add two” without a date is difficult to audit when a second broker, daylight transition or overnight event enters the record. The simplest reliable conversion is one another person can reverse from the saved inputs.
Start with an example Ghana interval from Monday 22:30 to Tuesday 01:15. On a plus-two server this begins Tuesday 00:30 and ends Tuesday 03:15. Filtering only Monday’s server rows would return no part of the intended interval. Filtering only Tuesday’s Ghana rows would omit the first ninety minutes. Convert both endpoints before selecting data.
When summarising intervals, specify whether the final timestamp is included. A fifteen-minute interval beginning at 09:00 is commonly treated as ending immediately before 09:15, with the 09:15 observation in the next interval. The convention should match how you process the feed. Otherwise a large boundary tick can be counted in two adjacent ranges and create an apparent sweep that never occurred under consistent aggregation.
Recover from an offset recorded with the wrong sign
Suppose your journal says the server was two hours behind Ghana, but the original paired screenshot reads server 12:20 and Ghana 10:20. The recorded sign was reversed. A conversion that already subtracted two from the correct server time may still contain the right Ghana output, while a spreadsheet formula built from the mistaken sign may be four hours off. Test one original pair before applying a blanket correction.
Create a three-row audit using one daytime observation, one just after server midnight and one near the relevant seasonal transition. Check whether the error is constant, date dependent or purely a date-boundary issue. An error appearing nightly may come from storing only time of day and losing the previous date. An error affecting only one broker can result from assigning a policy from a different server.
Preserve the pre-correction dataset when recalculating results. Report how many trades changed session classification, how many changed daily reference range and how many actual price decisions changed. Shifting a timestamp label is not the same as changing an underlying executed fill. A correctly documented repair should not rewrite the historical order identifier or price.
Annotate a kill-zone study with the rule it used
A school might teach a fixed 07:00 to 10:00 Ghana observation window for London, or noon to 15:00 Ghana for its New York study. Record those as fixed local study windows if that is how the method is defined. A session or event defined instead by a city’s civil clock requires conversion from that city for the actual date. The short label “London” cannot settle which convention a particular dataset used.
For the fixed Ghana example, a plus-two server maps 07:00–10:00 Ghana to 09:00–12:00 server. If the server later moves to plus three, the same Ghana window becomes 10:00–13:00 server. The window in the student’s Ghana diary stays unchanged. A spreadsheet that holds the old server hours constant will quietly shift the economic question being tested.
For an event explicitly defined as New York midnight, use the dated New York clock instead. At a plus-two server during US standard time, 05:00 Ghana becomes 07:00 server. During daylight time, 04:00 Ghana becomes 06:00 on an unchanged plus-two server. If the server also changes offset, recompute both conversions rather than memorising a single chart label.
Use chart time accurately in a dispute
A complaint that “my stop closed at 09:45” is ambiguous unless you state the clock. Include the platform identifier privately, original server timestamp, converted Ghana timestamp and source for the offset. Explain whether the compared time came from a quote chart, deal history, push notification or bank transaction. Each records a different event.
If a provider supplies a price trace in UTC, compare it with the converted deal timestamp before inspecting bid and ask. If its trace has only minute bars and the stop happened within that minute, state what the trace can establish and what remains unknown. Accurate clock conversion does not restore tick sequencing missing from the source.
At the end of an audit, a clear statement can resolve a surprising amount: the trade and event were aligned to the same instant, the two providers used different daily boundaries, and the remaining difference concerns the quote side at a particular tick. That focuses the next enquiry on the actual unresolved fact rather than a general disagreement about Ghana time.
Distinguish elapsed time from a local calendar label
A position opened at 23:55 Ghana and closed at 00:10 the next day was open for fifteen minutes. A journal that stores the two times without dates may subtract them and obtain a large negative number. Adding or subtracting a server offset preserves the fifteen-minute interval as long as both endpoints are converted correctly. Use full timestamps for duration calculations.
A daylight change can create an additional trap when working in a foreign civil timezone. The same displayed local clock hour can occur twice during a fall transition. Ghana’s GMT timeline does not repeat that hour. Recording the underlying UTC instant or a timestamp with its numeric offset makes the two observations distinct even if both foreign labels appear identical.
If the broker provides only a bare local server time during such an interval, look for a sequence identifier, a dated timezone rule or corroborating deal information. If you cannot distinguish the two possible instants, mark the timestamp ambiguous rather than assigning the occurrence that best fits a chart story. This limitation affects precise event studies more than it affects basic price arithmetic.
Finally, describe any time-based exclusion in the study report. A trade with an unknown exact minute can still support a check of gross pip profit if its fills are known. It should not be used as evidence that price reacted within a specified number of seconds of a release. Matching the claim to the timestamp evidence is the whole purpose of converting the clocks carefully.
An easy classroom test is to ask two people to mark the same completed candle independently. One uses a phone set to Accra and the other uses the desktop terminal’s crosshair. Compare the symbol, server, timeframe, candle opening time and the numeric high and low. A match in price with a fixed shift in the labels points to the clock conversion. Different highs and lows invite a feed or instrument check before changing the offset. This test also catches the common mistake of reading a candle’s closing minute as its label.
Server time questions
Is MT5 always GMT+2?
No. The trade server and date matter. Measure the actual offset or use documented terms for the specific server.
Does Ghana switch clocks when the US does?
Ghana stays on GMT. An event tied to New York local time can move by one hour on a Ghana clock.
Is the phone notification time the fill time?
A notification can arrive after a deal. Use the recorded deal timestamp and the correct server offset for execution analysis.
Can I align daily bars just by relabelling the time axis?
Relabelling timestamps does not change which observations were aggregated. Rebuild the interval if you need a common daily high or low.
What if the market is closed?
Use a dated broker source or wait for a fresh quote. A frozen last-tick time is poor evidence of the current offset.
Continue with the Ghana trading sessions guide and the session time converter. For related examples, see the economic calendar guide and the trading journal guide.
