Sophie
27 ottobre 2026 · 12 min di lettura
Your son texts you from Tokyo at 9 in the morning, and the message shows up in your thread as "yesterday, 11:12 PM". A colleague sends you a text from New York and it slots in above the one you had just sent, as though it came first. You're waiting for a login code and the timestamp shows a time that hasn't happened yet. Nothing is broken: the time displayed next to a text message is not the moment the sender hit send, it's the time the message centre (SMSC) of their carrier wrote into the message, using its own time zone — your phone merely converts it, sometimes badly.
Updated 27 October 2026.
Who decides the time shown next to a text message?
The sender's carrier's SMSC (Short Message Service Centre). When you tap "Send", your phone doesn't transmit any date: it sends the text and the recipient's number. The SMSC that receives the message adds a standardised field called the Service Centre Time Stamp, defined by specification 3GPP TS 23.040 from 3GPP, the body that standardises GSM and therefore SMS.
That field contains seven bytes: year, month, day, hour, minute, second, and then the message centre's offset from Coordinated Universal Time (UTC), expressed in quarter-hours. It's this last byte that causes all the trouble: it describes the server's time zone, not the sender's, and certainly not yours.
So your phone receives an absolute time and an offset. It converts that into your local time zone for display. Three places can get it wrong:
| Link in the chain | What it does | Possible error |
|---|---|---|
| Sender's SMSC | Timestamps the message | Misconfigured server, missing or wrong offset |
| Transit network | Relays the message | Does not normally alter the timestamp |
| Your phone | Converts and displays | Manual time zone, clock not synchronised |
In other words, when a text message's time looks absurd, the cause is almost always at your end of the chain, or at the point of origin, with a foreign carrier whose SMSC is misconfigured.
Why does a text from abroad show the wrong time?
Because some foreign SMSCs write a local time without correctly filling in the UTC offset, or set it to zero. Your phone then assumes the time it received is UTC and shifts it again by your own time zone. The result: a message sent from Mexico City or Manila arrives several hours out, sometimes dated the day before or the day after.
The most common cases:
- A message that jumps up the thread. A text timestamped in the past is sorted ahead of your own messages, since most apps sort by timestamp rather than by order of arrival.
- A message "from the future". An SMSC with a badly declared time zone ahead of yours produces a time that hasn't arrived yet where you are. Some conversation threads then pin it permanently at the top.
- A message dated yesterday. Classic on messages sent between Asia-Pacific and Europe: a 9 to 10 hour gap is enough to change the calendar date.
- A pending text released all at once. A message stored for several hours because the recipient was unreachable keeps the timestamp of its submission, not its delivery. The mechanism is explained in detail in our article on texts sent to a switched-off phone.
One detail makes the confusion worse: business messaging gateways (banks, delivery companies, web platforms) go through international aggregators. A "French" security code may perfectly well be timestamped by an SMSC located in the Netherlands, Ireland or Switzerland. The time shown then has nothing to do with where the company writing to you is based.
How does your phone know the time, exactly?
From the mobile network, if it's set up for it. GSM has included a mechanism called NITZ (Network Identity and Time Zone) from the start: the cell tower broadcasts UTC time and the country's time zone, and the phone aligns with it. That's what makes a mobile's clock update by itself when you land abroad.
The snag is that NITZ is optional. Not every carrier broadcasts it, some broadcast the wrong zone, others fail to apply daylight saving time. For several years now, Android and iOS have compensated with an estimate based on location and on NTP time servers, but that correction assumes an active data connection — which isn't the case if you've turned data off abroad to avoid the bill.
A phone left in airplane mode for a long stretch, with data off and no NITZ, drifts: its internal clock is no longer resynchronised. Once you're back, the texts received during that period keep an offset time.
That's why a mobile's clock is more reliable when roaming within Europe than on a long-haul trip: European Union networks broadcast NITZ very widely, and clock changes there are harmonised by Directive 2000/84/EC, applied everywhere on the last Sunday of October and of March. Outside the EU, daylight saving rules differ from one country to the next — and several countries have dropped it altogether.
For a long stay in a country that doesn't broadcast network time, a smartwatch with dual time zones solves the practical problem: it keeps an independent reference, handy for checking the gap between the time your phone shows and the real time.
The exact settings to check on Android and iPhone
In the vast majority of cases, this isn't a carrier problem but a time zone stuck on manual on the phone.
On Android (version 14 and later, Google Pixel and Samsung paths):
- Open Settings → System → Date & time (on Samsung: Settings → General management → Date and time).
- Turn on Set time automatically (or "Automatic date and time").
- Turn on Set time zone automatically.
- If the option "Use location to set time zone" is offered, enable it: it takes over when the network doesn't broadcast NITZ.
- Restart the phone, then check the clock before reopening Messages.
On iPhone (iOS 18 and later):
- Settings → General → Date & Time.
- Turn on Set Automatically.
- If the time zone is still wrong, turn the automatic setting off and back on; if nothing changes, check that Settings → Privacy & Security → Location Services → System Services → Setting Time Zone is enabled.
Important: fixing these settings does not rewrite the time on texts you've already received. The timestamp is stored with the message in the app's database. Older messages will keep showing the wrong time; new ones will be correct. No consumer app can cleanly change the timestamp of a received text message — and any app that promises to do so deserves the utmost suspicion regarding the access it requests to your messages.
Does the time on a text message count as evidence?
Only with caution. The timestamp you see on screen is data supplied by a third party (the sender's SMSC) and reconverted by your device: it guarantees neither the exact second nor the original time zone. A screenshot of a text message is routinely produced in court, but it's the consistency of the whole that matters, not the minute displayed.
In practice, if the time of a message genuinely matters to you (a commercial dispute, a cooling-off period, proof that you took a step), two things carry more weight than your screen:
- the connection data retained by the carrier, which it can produce on a court order — the framework for that retention is set out by Arcep and by the French postal and electronic communications code;
- a formal record drawn up by a judicial commissioner, who timestamps the inspection themselves.
To archive an important conversation for the long term, exporting it to storage you control is preferable to the phone's memory: a backup on an external SSD drive or a printout avoids losing everything along with the device. Note that with RCS, as with encrypted messaging apps, the timestamp depends on the service's server, with exactly the same limitations.
Did the clock change on 25 October 2026 have any effect?
Yes, but a limited and short-lived one. France switched to winter time overnight from Saturday 24 to Sunday 25 October 2026, at 3 AM, with the clocks going back to 2 AM. During that night, two hours share the same name: a text sent at 2:30 AM "summer time" and another at 2:30 AM "winter time" display at the same time even though an hour separates them.
The practical consequences to be aware of:
- Conversations from that night may appear out of order, especially between people whose phones didn't switch at the same instant.
- Scheduled text messages set up in a messaging app are triggered on the phone's local time: those due during the "doubled" hour may go out an hour early or an hour late. If you use delayed sending, now is the time to check your schedules. The topic is covered in our guide on the value of scheduled SMS.
- The gap with your contacts outside the EU changes. The United Kingdom and Switzerland switch on the same day as France; the United States and Canada, on the other hand, only changed their clocks on 1 November 2026. Between 25 October and 1 November, the Paris–New York gap is therefore 5 hours, not 6. Your morning message still arrives in the middle of the night for the person you're writing to.
A small multi-time-zone wall clock, or simply a second clock added in your phone's Clock app, saves you doing that calculation in your head every time.
How do you avoid time misunderstandings in international texts?
Four habits are enough, and they cost nothing.
- Spell the time out in the message, with the zone: "call at 3 PM Paris time" rather than "call at 3 PM". It's the only piece of information no SMSC can distort.
- Prefer UTC for technical or professional appointments spanning several countries.
- Save your contacts in full international format (
+33,+1,+52…). It doesn't affect the timestamp, but it avoids the sending failures that make a message look as though it "went out later". The format is explained in detail in our article on badly saved foreign numbers. - Don't rely on delivery receipts to reconstruct a timeline: they indicate delivery to the handset, not reading, and they are especially misleading internationally, as we explained regarding delivery receipts abroad.
If you write abroad a lot without a suitable plan, sending a text from our home page remains a direct solution, and the service FAQ answers questions about formats and delivery times.
What if the time stays wrong on every message?
Then the problem is local, and the diagnostic process is short:
| Symptom | Likely cause | What to do |
|---|---|---|
| The phone's clock is right, the texts are offset | Timestamp from the sender's SMSC | Nothing to do at the recipient's end |
| The phone's clock is wrong too | Time zone on manual, no NITZ | Re-enable automatic date and time |
| Offset of exactly one hour | Daylight saving not applied | Check the time zone (Europe/Paris, not a fixed UTC+1) |
| Offset of several hours after a trip | Clock not resynchronised | Restart with the mobile network active |
| Only one sender's messages are offset | Misconfigured messaging gateway | Report it to the sending company |
A restart with the mobile network active — not on Wi-Fi alone — is enough in most cases: it's when it reattaches to the network that the phone re-reads the time broadcast by the cell tower. If you often travel with a secondary device that stays off-network for long stretches, a compact power bank at least lets you switch it on when you arrive so it can resynchronise before the messages pour in.
Frequently asked questions
Why does my text message show yesterday's time?
Because the timestamp written by the sender's message centre is in a time zone behind yours, or because the UTC offset wasn't transmitted. With a gap of 8 to 12 hours, the time crosses midnight and the date changes.
Can you correct the time on a text you've already received?
No, not cleanly. The timestamp is saved with the message. Fixing the phone's time zone only affects messages received afterwards. Be wary of apps that claim otherwise: they demand full access to your texts.
Does a wrong time mean my text message was intercepted?
No. An offset timestamp is a time zone problem, not a security one. A delayed or badly dated text indicates no interception whatsoever.
Does RCS show a more reliable time than SMS?
Often yes, because the timestamp comes from the messaging service's server rather than a carrier SMSC, but the principle is the same: it's a server time converted by your phone. The discrepancies are simply rarer.
Should you turn off automatic time when travelling?
No, quite the opposite: leave it on. A manually set time zone is the leading cause of wrong times after a trip, because it never changes back by itself when you return.
