Telegram has no public lookup of registration dates by ID. What exists are known pairs of an ID and a registration time. Here are all 59 that our checker uses, from November 2013 to November 2025.
Download the data
Columns: user_id, reference_date_utc, checker_month_utc, adjusted_monotonic and source. The file is built directly from the data in the Telegram account age checker, so the two always match.
Telegram user ID range by year
Each row counts the reference points that fall in that year. There are no points for 2018 or 2020, so those years have no row.
| Year | Reference points | Lowest ID | Highest ID |
|---|---|---|---|
| 2013 | 2 | 2,768,409 | 7,679,610 |
| 2014 | 8 | 11,538,514 | 63,263,518 |
| 2015 | 14 | 101,260,938 | 143,445,125 |
| 2016 | 12 | 148,670,295 | 328,594,461 |
| 2017 | 5 | 337,808,429 | 400,169,472 |
| 2019 | 1 | 805,158,066 | 805,158,066 |
| 2021 | 2 | 1,974,255,900 | 5,027,000,000 |
| 2022 | 4 | 5,170,000,000 | 5,720,000,000 |
| 2023 | 4 | 5,870,000,000 | 6,647,000,000 |
| 2024 | 4 | 6,718,000,000 | 7,665,000,000 |
| 2025 | 3 | 7,908,000,000 | 8,355,000,000 |
All 59 reference points
| User ID | Reference date | Month used by the checker |
|---|---|---|
| 2,768,409 | 2013-11-01 | November 2013 |
| 7,679,610 | 2013-12-31 | December 2013 |
| 11,538,514 | 2014-01-31 | January 2014 |
| 15,835,244 | 2014-02-20 | February 2014 |
| 23,646,077 | 2014-02-26 | February 2014 |
| 38,015,510 | 2014-03-01 | March 2014 |
| 44,634,663 | 2014-05-05 | May 2014 |
| 46,145,305 | 2014-05-15 | May 2014 |
| 54,845,238 | 2014-09-20 | September 2014 |
| 63,263,518 | 2014-10-27 | October 2014 |
| 101,260,938 | 2015-03-06 | March 2015 |
| 101,323,197 | 2015-03-12 | March 2015 |
| 103,151,531 | 2015-06-04 | June 2015 |
| 103,258,382 | 2015-05-27 | June 2015 (adjusted) |
| 109,393,468 | 2015-08-08 | August 2015 |
| 111,220,210 | 2015-04-20 | August 2015 (adjusted) |
| 112,594,714 | 2015-08-15 | August 2015 |
| 116,812,045 | 2015-07-24 | August 2015 (adjusted) |
| 122,600,695 | 2015-07-24 | August 2015 (adjusted) |
| 124,872,445 | 2015-08-18 | August 2015 |
| 125,828,524 | 2015-10-04 | October 2015 |
| 130,029,930 | 2015-09-03 | October 2015 (adjusted) |
| 133,909,606 | 2015-10-07 | October 2015 |
| 143,445,125 | 2015-12-01 | December 2015 |
| 148,670,295 | 2016-01-07 | January 2016 |
| 152,079,341 | 2016-01-21 | January 2016 |
| 157,242,073 | 2015-11-06 | January 2016 (adjusted) |
| 171,295,414 | 2016-03-08 | March 2016 |
| 181,783,990 | 2016-04-09 | April 2016 |
| 222,021,233 | 2016-06-08 | June 2016 |
| 225,034,354 | 2016-06-18 | June 2016 |
| 278,941,742 | 2016-09-09 | September 2016 |
| 285,253,072 | 2016-10-18 | October 2016 |
| 294,851,037 | 2016-11-20 | November 2016 |
| 297,621,225 | 2016-12-15 | December 2016 |
| 328,594,461 | 2016-12-28 | December 2016 |
| 337,808,429 | 2017-02-21 | February 2017 |
| 341,546,272 | 2017-02-22 | February 2017 |
| 352,940,995 | 2017-02-23 | February 2017 |
| 369,669,043 | 2017-03-30 | March 2017 |
| 400,169,472 | 2017-07-30 | July 2017 |
| 805,158,066 | 2019-07-15 | July 2019 |
| 1,974,255,900 | 2021-10-12 | October 2021 |
| 5,027,000,000 | 2021-12-15 | December 2021 |
| 5,170,000,000 | 2022-02-15 | February 2022 |
| 5,351,000,000 | 2022-05-15 | May 2022 |
| 5,469,000,000 | 2022-08-15 | August 2022 |
| 5,720,000,000 | 2022-11-15 | November 2022 |
| 5,870,000,000 | 2023-02-15 | February 2023 |
| 6,001,000,000 | 2023-05-15 | May 2023 |
| 6,523,000,000 | 2023-08-15 | August 2023 |
| 6,647,000,000 | 2023-11-15 | November 2023 |
| 6,718,000,000 | 2024-02-15 | February 2024 |
| 7,095,000,000 | 2024-05-15 | May 2024 |
| 7,358,000,000 | 2024-08-15 | August 2024 |
| 7,665,000,000 | 2024-11-15 | November 2024 |
| 7,908,000,000 | 2025-03-31 | March 2025 |
| 8,190,000,000 | 2025-08-15 | August 2025 |
| 8,355,000,000 | 2025-11-15 | November 2025 |
6 rows are marked as adjusted. Their reference date is earlier than the date of a lower ID, so the checker carries the latest date forward. That keeps the series in order: a higher ID never maps to an earlier month.
How to read the table
- Find the numeric user ID of the account.
- Find the two rows it falls between in the full table.
- Read the months in those two rows. The account was probably registered between them.
The age checker does the same steps for you and shows the window.
What the table cannot tell you
- It gives a period, not a date. IDs were issued roughly in sequence, not strictly, which is why some rows needed adjusting.
- Coverage is uneven. Windows are short for early years and up to about two years wide between mid-2017 and late 2021, where public points are sparse. From December 2021 each row is the median ID of one quarter, and the checker shows about four months either way.
- It stops at November 2025. IDs above 8,355,000,000 are outside the data.
- It covers user accounts only. Channels and groups have their own IDs, which this data does not include, so check them with the group age checker or the steps in how to check a creation date.
Frequently asked questions
How accurate is a creation date based on a Telegram user ID?
It is an estimate. The result is the window between the two nearest reference points, and that window can be months or, in sparse periods, years wide.
Why is there no data after November 2025?
The public reference set ends there. IDs above 8,355,000,000 cannot be placed reliably, so neither this table nor the checker estimates them.
Can I reuse the CSV?
Yes. It is free to reuse with attribution to agedsocials.com and to the tdage and CreationDate projects, whose reference data is under the MIT License.
Does a low user ID say anything about an account's condition?
No. An ID only suggests when an account was registered. It says nothing about restrictions, history or who controls the account today.
Telegram