Telegram RegisterThe public register of Telegram
Telegram profile photo for НА КАРАНДАШЕ✍🏻

Channel

НА КАРАНДАШЕ✍🏻

@nakarandasherus

On this record: Topic · Growth · What this channel posts · Posts edited after publishing · Posts recorded as deleted · Citations · Cite this entry

12,780subscribers

+597 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1001439401552
TypeChannel
Username@nakarandasherus
DescriptionПо поводу рекламы: @reklam_mgr Канал создан для спортсменов, родителей, скаутов, тренеров, менеджеров, агентов, а его цель - помощь в поиске и отслеживании успехов юных футболистов с любой точки страны!
Created3 April 2019 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live15 November 2026
Measurements held64
Confirmed unchanged1 time, most recently 15 November 2026
On Telegramt.me/nakarandasherus

Topic

Sports — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 100% 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

12,18112,83612,508.512,7806 August 202615 November 2026
64 measurements spanning 101 days, net +597. 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 12,083–12,934 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 64
Measured (UTC)SubscribersChange
15 Nov 2026, 18:0912,780+13
12 Nov 2026, 09:4112,767+28
10 Nov 2026, 10:0512,739+5
8 Nov 2026, 19:3112,734-4
7 Nov 2026, 11:1712,738-18
6 Nov 2026, 11:2612,756-9
5 Nov 2026, 08:4612,765+1
4 Nov 2026, 10:0412,764-2
3 Nov 2026, 07:5712,766+5
2 Nov 2026, 10:3912,761-7
1 Nov 2026, 08:1712,768-9
31 Oct 2026, 10:2812,777+3
29 Oct 2026, 09:0012,774-14
28 Oct 2026, 06:3012,788-15
27 Oct 2026, 07:1612,803+7
26 Oct 2026, 09:1412,796-6
25 Oct 2026, 09:5912,802-1
24 Oct 2026, 12:4812,803+1
23 Oct 2026, 15:0612,802+5
22 Oct 2026, 14:5112,797first reading

What this channel posts

Photos
≈2,580
Videos
≈184
Links
≈583

Lifetime counters from Telegram’s own channel header, read 17 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.

Posts edited after publishing

@nakarandasherus edited 3 posts after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
30 August 2026

Posts recorded as deleted after publishing

We recorded 2 posts on @nakarandasherus as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
2 September 2026
Most recent seen missing
8 November 2026
Median time before seen missing
14 hours
Seen missing in the last 30 days
1

Mentions

Named by 7 registered channels — 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. The 0 listed below are the most frequent namers; the rest are counted above but not each listed.

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

“НА КАРАНДАШЕ✍🏻” (@nakarandasherus), 12,780 subscribers as measured 15 November 2026. Telegram Register, tgregister.com/channel/nakarandasherus.

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.