Telegram RegisterThe public register of Telegram
Telegram profile photo for ɐ̖sǝ

Channel

ɐ̖sǝ

@Never_12_Tg

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

971subscribers

+785 since we began measuring on 13 October 2026

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

Register entry

Telegram ID-1002241020739
TypeChannel
Username@Never_12_Tg
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded13 October 2026
Last confirmed live28 October 2026
Measurements held5
Confirmed unchanged1 time, most recently 28 October 2026
On Telegramt.me/Never_12_Tg

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 28 October 2026 and assigned it the closest of 31 fixed categories, at 59% 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

186993589.513 October 2026 — 186 subscribers13 October 2026 — 186 subscribers14 October 2026 — 392 subscribers21 October 2026 — 993 subscribers28 October 2026 — 971 subscribers97113 October 202628 October 2026
5 measurements spanning 14 days, net +785. 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 65–1,114 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Oct 2026, 01:59971-22
21 Oct 2026, 19:39993+601
14 Oct 2026, 14:37392+206
13 Oct 2026, 16:22186no change
13 Oct 2026, 15:47186first reading

Engagement

20 posts held, back to 11 May 2026 — 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 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
5.15%
avg views ÷ 971 subscribers
Avg views / post
50.0
6 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
6
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views — note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 13 October 2026
Posts held20 (11 May 2026 – 13 October 2026)
Views total300
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken13 Oct 2026, 16:22 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

13 Oct 2026, 09:35 UTC52 viewsread 13 October 2026

«le silence est parfois la plus belle des réponses» иногда тишина-это лучший ответ.

12 Oct 2026, 20:31 UTC56 viewsread 13 October 2026

и дорога ведущая в никуда начинает обретать своё направление.

11 Oct 2026, 21:34 UTC52 viewsread 13 October 2026

пусть теперь будет настолько хорошо, насколько я ещё не знаю.

23 Jun 2026, 18:20 UTC160 viewsread 13 October 2026

и те, кто танцевал, казались сумасшедшими тем, кто не мог слышать музыку.

16 Jun 2026, 19:22 UTC168 viewsread 13 October 2026

в моих зрачках — лишь мне понятный сон в них мир видений зыбких и обманных таких же без конца непостоянных как дымка, что скрывает горный склон.

10 Jun 2026, 19:45 UTC129 viewsread 13 October 2026

как хорошо, что некого винить, как хорошо, что ты никем не связан, как хорошо, что до смерти любить тебя никто на свете не обязан.

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

Mentions

Named by 2 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.

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

“ɐ̖sǝ” (@Never_12_Tg), 971 subscribers as measured 28 October 2026. Telegram Register, tgregister.com/channel/Never_12_Tg.

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.