12 Apr 2018, 09:44 UTC≈82,900 viewsread 6 August 2026
http://telegra.ph/Kirpich-48-04-12
Channel
ЕГЭ РУССКИЙ ЯЗЫК
@egerussia
On this record: Growth · Engagement · Posts · Cite this entry
1,354subscribers
-5 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
Register entry
| Telegram ID | -1001109731414 |
|---|---|
| Type | Channel |
| Username | @egerussia |
| Created | Between 1 February 2017 and 22 February 2018— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 24 August 2026 |
| Measurements held | 7 |
| Confirmed unchanged | 1 time, most recently 24 August 2026 |
| On Telegram | t.me/egerussia |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 24 Aug 2026, 22:45 | 1,354 | -1 |
| 21 Aug 2026, 10:35 | 1,355 | -1 |
| 18 Aug 2026, 16:13 | 1,356 | -1 |
| 15 Aug 2026, 20:27 | 1,357 | -1 |
| 9 Aug 2026, 05:50 | 1,358 | -1 |
| 6 Aug 2026, 08:00 | 1,359 | no change |
| 6 Aug 2026, 01:59 | 1,359 | first reading |
Engagement
20 posts held, back to 22 February 2018 — the 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 12 April 2018. An engagement rate over an empty window would be a number about nothing.
Recent posts
7 Apr 2018, 17:10 UTC≈81,800 viewsread 6 August 2026
http://telegra.ph/Kirpich-47-04-07
3 Apr 2018, 16:30 UTC≈61,100 viewsread 6 August 2026
http://telegra.ph/Kirpich-46-04-03
29 Mar 2018, 16:48 UTC≈50,100 viewsread 6 August 2026
http://telegra.ph/Kirpich-45-03-29
28 Mar 2018, 13:10 UTC≈41,200 viewsread 6 August 2026
http://telegra.ph/Kirpich-44-03-28
27 Mar 2018, 12:41 UTC≈35,200 viewsread 6 August 2026
http://telegra.ph/Kirpich-43-03-26-2
27 Mar 2018, 12:41 UTC≈30,800 viewsread 6 August 2026
http://telegra.ph/Kirpich42-03-27
21 Mar 2018, 21:53 UTC≈28,000 viewsread 6 August 2026
http://telegra.ph/Kirpich-41-03-21-3
14 Mar 2018, 20:25 UTC≈27,000 viewsread 6 August 2026
http://telegra.ph/Kirpich-40-03-14
14 Mar 2018, 20:23 UTC≈24,400 viewsread 6 August 2026
http://telegra.ph/Kirpich-39-03-14
12 Mar 2018, 20:08 UTC≈22,000 viewsread 6 August 2026
Photo
Photo, posted without a caption
12 Mar 2018, 20:08 UTC≈22,200 viewsread 6 August 2026
Ребята, рассказываю про планы на март в мастер-группе, потому что через неделю запись закроется: 💡 В марте каждый день соответствует определенной работе: 🔹 Каждый понедельник вы решаете УПРАЖНЕНИЕ 🔹 Каждый вторник, четверг и каждое воскресенье у нас вебинар 🔹 Каждую пятницу АУДИТ 🔹 Каждую среду и субботу мы работаем над ТВОИМИ ОШИБКАМИ и закрываем пробелы в орфографии (8-14) и пунктуации (15-19) ☝ ИТОГО: 🔹12 ВЕБ…
Showing the 12 most recent of 20 posts we hold for @egerussia. 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 24 August 2026 — this entry's latest reading, not the date you are reading this.
“ЕГЭ РУССКИЙ ЯЗЫК” (@egerussia), 1,354 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/egerussia.
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.