Telegram RegisterThe public register of Telegram

Channel

eclipse

@sranchik6

Not marked by Telegram, checked 15 August 2026

On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry

2,806subscribers

Risers and fallers across the register · movement among entries of 1,000–3,162.

Register entry

Telegram ID-1002211428798
TypeChannel
Username@sranchik6
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live14 August 2026
Measurements held1
On Telegramt.me/sranchik6

Growth

Growth history is still building. We hold one measurement for this entry. A trend needs at least two, taken days apart — so this will fill in on its own rather than being estimated. We do not publish numbers we have not measured.

Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
14 Aug 2026, 07:452,806first reading

Engagement

20 posts held, back to 12 May 2025 — 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 19 June 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Photos
88

Lifetime counters from Telegram’s own channel header, read 14 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.

Recent posts

Showing the 12 most recent of 20 posts we hold for @sranchik6. 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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

УННВ | Андеграунд | Эстетика
@YNNV_REMiXX · 117,157
Telegram ranks this channel #28 of 51 here — alongside 50 others — read 14 August 2026
Плейлист 🎧 | Музыка для души
@playlist_muzykaa · 154,296
Telegram ranks this channel #39 of 59 here — alongside 58 others — read 14 August 2026
Montteci🔥 | Музыка | Треки
@montteci_music · 113,142
Telegram ranks this channel #41 of 63 here — alongside 62 others — read 14 August 2026
Новости • Красногорск • Митино
@krasno_info · 111,636
Telegram ranks this channel #51 of 55 here — alongside 54 others — read 14 August 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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 14 August 2026 — this entry's latest reading, not the date you are reading this.

“eclipse” (@sranchik6), 2,806 subscribers as measured 14 August 2026. Telegram Register, tgregister.com/channel/sranchik6.

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.