Telegram RegisterThe public register of Telegram
Telegram profile photo for ОСЧ (мск)

Channel

ОСЧ (мск)

@chertovaigla

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

705subscribers

+13 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001706147513
TypeChannel
Username@chertovaigla
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live15 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 15 September 2026
On Telegramt.me/chertovaigla

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 20 September 2026 and assigned it the closest of 31 fixed categories, at 76% 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 why it has no browse page of its own yet.

Growth

6917056986 August 2026 — 692 subscribers6 August 2026 — 692 subscribers7 August 2026 — 691 subscribers14 August 2026 — 696 subscribers29 August 2026 — 700 subscribers15 September 2026 — 705 subscribers6 August 202615 September 2026
6 measurements spanning 40 days, net +13. 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 689–707 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
15 Sept 2026, 23:37705+5
29 Aug 2026, 23:43700+4
14 Aug 2026, 10:27696+5
7 Aug 2026, 17:06691-1
6 Aug 2026, 23:16692no change
6 Aug 2026, 23:03692first reading

Engagement

19 posts held, back to 15 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of 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 19 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

482 reactions across 19 posts, in 3 distinct kinds. The most used accounts for 62.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 539333577957549903230362.9%
custom 543625978151596560516834.9%
custom 5436109831322760030112.28%

Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.

Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.

Coverage. Reactions were read on 19 of the 19 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 482 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 19 most recent posts we hold, published 15 July 2026 to 6 August 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

6 Aug 2026, 20:22 UTC126 views24 reactionsread 6 August 2026
Photo

Ого Фрихэнд

custom 539333577957549903217custom 54362597815159656057

4 Aug 2026, 14:59 UTC216 views3 reactionsread 6 August 2026

Хочу крутой фотосет Можем договориться по бартеру на татуху Пиши @hoboto

custom 53933357795754990323

3 Aug 2026, 14:56 UTC274 views23 reactionsread 6 August 2026
Video message

Video message, posted without a caption

custom 539333577957549903223

3 Aug 2026, 13:55 UTC270 views30 reactionsread 6 August 2026
Video

Video, posted without a caption

custom 539333577957549903222custom 54362597815159656058

2 Aug 2026, 11:32 UTC282 views19 reactionsread 6 August 2026

Сегодня мне приснилось что я курил сигареты...

custom 543625978151596560513custom 53933357795754990326

31 Jul 2026, 19:40 UTC329 views30 reactionsread 6 August 2026
Photo

Photo, posted without a caption

custom 539333577957549903220custom 543625978151596560510

27 Jul 2026, 15:33 UTC438 views17 reactionsread 6 August 2026
Video message

Video message, posted without a caption

custom 543625978151596560512custom 53933357795754990325

26 Jul 2026, 11:43 UTC457 views52 reactionsread 6 August 2026
Photo

Капец я восемь лет назад этюдики живые писал

custom 539333577957549903242custom 543625978151596560510

24 Jul 2026, 19:36 UTC436 views4 reactionsread 6 August 2026

Ой там фотография не обрезалась оказывается....

custom 54362597815159656054

24 Jul 2026, 07:19 UTC457 views14 reactionsread 6 August 2026
Photo

Друзья, у меня на следующий месяц свободно 10 мест на сеансы И 4 на мини тату Выбирай любую дату в календаре Чтобы записаться на тату пиши @hoboto

custom 53933357795754990327custom 54362597815159656057

22 Jul 2026, 21:02 UTC440 views29 reactionsread 6 August 2026
Photo

Один сеанс Фрихэнд Перекрытие Фото до в комментах

custom 539333577957549903220custom 54362597815159656059

22 Jul 2026, 20:47 UTC407 views33 reactionsread 6 August 2026
Photo

Один сеанс Не фрихэнд

custom 543625978151596560524custom 53933357795754990329

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

Forward network

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

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

“ОСЧ (мск)” (@chertovaigla), 705 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/chertovaigla.

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.