Telegram RegisterThe public register of Telegram
Telegram profile photo for ШТОРМ ЧАТ | 𝐄𝐋𝐈𝐓𝐄

Supergroup

ШТОРМ ЧАТ | 𝐄𝐋𝐈𝐓𝐄

@chilovy_work

On this record: Topic · Growth · Engagement · Citations · Cite this entry

10,209members

-666 since we began measuring on 7 August 2026

533 online right now

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1003725479396
TypeSupergroup
Username@chilovy_work
CreatedBetween 1 February 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded19 August 2026
Last confirmed live29 October 2026
Measurements held50
Confirmed unchanged1 time, most recently 29 October 2026
On Telegramt.me/chilovy_work

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 10 September 2026 and assigned it the closest of 31 fixed categories, at 99% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and the other topics.

Growth

10,20914,35512,2827 August 2026 — 10,875 members7 August 2026 — 10,896 members9 August 2026 — 11,007 members10 August 2026 — 11,111 members11 August 2026 — 11,311 members12 August 2026 — 11,918 members13 August 2026 — 12,374 members14 August 2026 — 12,757 members16 August 2026 — 13,142 members17 August 2026 — 13,439 members18 August 2026 — 13,716 members19 August 2026 — 13,893 members19 August 2026 — 13,893 members20 August 2026 — 14,134 members21 August 2026 — 14,290 members22 August 2026 — 14,355 members24 August 2026 — 14,272 members25 August 2026 — 14,262 members26 August 2026 — 14,260 members27 August 2026 — 14,258 members28 August 2026 — 14,254 members29 August 2026 — 14,236 members30 August 2026 — 14,211 members31 August 2026 — 14,139 members1 September 2026 — 14,121 members2 September 2026 — 14,047 members4 September 2026 — 14,024 members6 September 2026 — 14,036 members9 September 2026 — 14,017 members12 September 2026 — 14,052 members13 September 2026 — 14,046 members15 September 2026 — 14,065 members17 September 2026 — 14,074 members27 September 2026 — 13,898 members4 October 2026 — 13,921 members9 October 2026 — 13,886 members13 October 2026 — 13,657 members14 October 2026 — 13,653 members15 October 2026 — 13,643 members16 October 2026 — 13,603 members17 October 2026 — 13,566 members18 October 2026 — 13,550 members19 October 2026 — 13,535 members20 October 2026 — 13,529 members23 October 2026 — 13,510 members24 October 2026 — 10,711 members25 October 2026 — 10,438 members26 October 2026 — 10,326 members27 October 2026 — 10,274 members29 October 2026 — 10,209 members7 August 202629 October 2026
50 measurements spanning 82 days, net -666. 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 9,587–14,977 and does not start at zero.
Measurement log — every members count we have recorded, most recent 20 of 50
Measured (UTC)MembersChange
29 Oct 2026, 03:5010,209-65
27 Oct 2026, 23:1110,274-52
26 Oct 2026, 21:4610,326-112
25 Oct 2026, 20:1910,438-273
24 Oct 2026, 22:2510,711-2,799
23 Oct 2026, 20:3513,510-19
20 Oct 2026, 11:3413,529-6
19 Oct 2026, 12:5013,535-15
18 Oct 2026, 14:5413,550-16
17 Oct 2026, 14:0713,566-37
16 Oct 2026, 15:5913,603-40
15 Oct 2026, 15:4113,643-10
14 Oct 2026, 18:1813,653-4
13 Oct 2026, 05:5913,657-229
9 Oct 2026, 02:5713,886-35
4 Oct 2026, 19:0113,921+23
27 Sept 2026, 03:1713,898-176
17 Sept 2026, 10:5614,074+9
15 Sept 2026, 10:1814,065+19
13 Sept 2026, 16:0114,046first reading

Engagement

No public post preview. We read this entry on 19 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

A mention is a weaker signal than a forward and is counted separately for that reason — naming a channel is not republishing it, and a handle in a post body is easy to place deliberately. The post counts beside each row below are distinct posts in which the handle appeared, from posts we have read on both sides — the “Named by N registered channels” figure above is a different count, of distinct NAMING CHANNELS rather than posts, and is not the sum of the rows under it.

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

“ШТОРМ ЧАТ | 𝐄𝐋𝐈𝐓𝐄” (@chilovy_work), 10,209 members as measured 29 October 2026. Telegram Register, tgregister.com/channel/chilovy_work.

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.