Telegram RegisterThe public register of Telegram
Telegram profile photo for Что происходит?

Channel

Что происходит?

@tickets2018

On this record: Growth · Engagement · Posts · Cite this entry

298subscribers

+1 since we began measuring on 8 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001121988951
TypeChannel
Username@tickets2018
CreatedBetween 1 June 2017 and 3 December 2017— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live28 August 2026
Measurements held4
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/tickets2018

Growth

2962982978 August 2026 — 297 subscribers9 August 2026 — 297 subscribers22 August 2026 — 296 subscribers28 August 2026 — 298 subscribers8 August 202628 August 2026
4 measurements spanning 20 days, net +1. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 296–298 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 07:55298+2
22 Aug 2026, 05:36296-1
9 Aug 2026, 04:11297no change
8 Aug 2026, 12:30297first reading

Engagement

20 posts held, back to 3 December 2017the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 2 March 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

2 Jun 2021, 12:49 UTCviews —

Что происходит? pinned «https://t.me/joinchat/ApIHAP9CPtBiMDQy Норм чат с билетами на Евро 2020»

2 Jun 2021, 06:46 UTC≈1,280 viewsread 8 August 2026

https://t.me/joinchat/ApIHAP9CPtBiMDQy Норм чат с билетами на Евро 2020

23 Sept 2020, 14:14 UTC≈1,950 viewsread 8 August 2026

2 билеты 3 кат на супер кубок УЕФА Бавария - Севилья.

11 Jun 2018, 11:19 UTC≈5,270 viewsread 8 August 2026

https://t.me/saleWC2018 все вступили? Очень активный чат с покупкой продажей билетов на ЧМ2018!

28 May 2018, 08:35 UTC≈6,050 viewsread 8 August 2026

https://t.me/joinchat/Gw9wiBDpB0DImeblqaTNGA ЧАТ В ТЕЛЕГРАМЕ. ОБМЕН-ПРОДАЖА. ОТВЕЧАЕМ НА ВСЕ ВОПРОСЫ ЧМ 2018

12 May 2018, 21:02 UTC≈7,020 viewsread 8 August 2026

Есть информация, что через часа 3 будут билеты на оф. сайте! Проверим

13 Mar 2018, 07:53 UTC≈7,850 viewsread 8 August 2026

http://ru.fifa.com/worldcup/organisation/ticketing/purchase.html Финальная продажа билетов на ЧМ2018! Всем удачи!

Showing the 12 most recent of 20 posts we hold for @tickets2018. View and reaction counts are the latest single reading for each post, not a live figure, and a recent post is still accumulating both. A view count marked was rounded by Telegram before we ever saw it — t.me prints views in full below 1,000 and to three significant figures above, so ≈1,200,000 means somewhere between 1,150,000 and 1,249,999. Unmarked counts are exact. Text is reproduced from the public post preview and truncated for length.

Cite this entry

A live page changes as we take new readings, so a citation should name the measurement it is based on, not just the URL. The line below cites the subscriber count as measured 28 August 2026 — this entry's latest reading, not the date you are reading this.

“Что происходит?” (@tickets2018), 298 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/tickets2018.

Full measurement history, CC BY 4.0. Every reading this register holds for this entry, not just the latest one, as a dated, downloadable record: CSV · JSON. Free to use with attribution to tgregister.com. Each file carries its own generation timestamp, which is the figure to cite for exactly when the data was retrieved.