Your Discord bot's timestamp says the year 58970 (I tested 16 edge cases)
Discord turns <t:1798765200:F> into a date shown in each reader's own time zone. The format is documented, but what Discord does with bad input isn't. Bots generate these strings, and bots get the input wrong, so on 4 November 2026 I sent 16 malformed or extreme codes to a private server from the Discord web client and read back what rendered. Code What it tests Discord showed <t:1798765200:F>…
Discord's bot-generated timestamps can display years far in the future due to a bug with handling malformed or extreme codes. The format is documented, but Discord's behavior with bad input is unclear. A reporter tested 16 edge cases on November 4, 2026.
The bot shows normal dates for valid inputs, such as "Friday, January 1, 2027 at 6:30 AM" for "t:1798765200:F". However, when using milliseconds instead of seconds, Discord renders the year "58970" on "Tuesday, August 7, 58970 at 9:30 PM", nearly 57,000 years ahead. Zero and negative values show dates from December 31, 1969.
Beyond JavaScript's date limits, Discord still displays valid years. For example, "Tuesday, January 19, 2038 at 8:44 AM" for "t:2147483648:F", and "Saturday, September 13, 275760" for "t:8640000000000:F". Even one second past these limits is displayed correctly as raw text.
However, not all valid codes render as expected. In some cases like poll questions, answers, thread titles, server nicknames, and custom statuses, Discord displays the code as raw text instead of a formatted date. This includes messages, thread messages, and channel topics, but not bot embeds or mobile app interfaces.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
