Telegram RegisterThe public register of Telegram
Telegram profile photo for Сергей Камелин

Channel

Сергей Камелин

@sergei_kamelin

Has discussion group

On this record: Topic · Growth · Engagement · Telegram's recommendations · Cite this entry

770subscribers

-5 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1001719309276
TypeChannel
Username@sergei_kamelin
Created11 March 2022 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded10 October 2026
Last confirmed live12 November 2026
Measurements held11
Confirmed unchanged1 time, most recently 12 November 2026
On Telegramt.me/sergei_kamelin

Topic

Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 12 October 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

770777773.57 August 2026 — 775 subscribers14 August 2026 — 776 subscribers4 September 2026 — 777 subscribers13 September 2026 — 776 subscribers27 September 2026 — 777 subscribers7 October 2026 — 776 subscribers10 October 2026 — 776 subscribers14 October 2026 — 775 subscribers21 October 2026 — 773 subscribers5 November 2026 — 772 subscribers12 November 2026 — 770 subscribers7 August 202612 November 2026
11 measurements spanning 97 days, net -5. 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 769–778 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Nov 2026, 13:47770-2
5 Nov 2026, 07:18772-1
21 Oct 2026, 03:37773-2
14 Oct 2026, 05:37775-1
10 Oct 2026, 04:43776no change
7 Oct 2026, 02:58776-1
27 Sept 2026, 03:39777+1
13 Sept 2026, 04:00776-1
4 Sept 2026, 08:17777+1
14 Aug 2026, 03:27776+1
7 Aug 2026, 06:30775first reading

Engagement

Posts not read yet. This entry is on the register from its profile alone; the post reader has not reached it. Engagement figures appear here once posts have actually been measured — we do not publish a rate before we have the readings behind it.

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.

Лимаренко Brief
@limarenko_official · 34,049
Telegram ranks this channel #93 of 95 here — alongside 94 others — read 3 September 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list 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 12 November 2026 — this entry's latest reading, not the date you are reading this.

“Сергей Камелин” (@sergei_kamelin), 770 subscribers as measured 12 November 2026. Telegram Register, tgregister.com/channel/sergei_kamelin.

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.