Telegram RegisterThe public register of Telegram
Telegram profile photo for Забыто

Channel

Забыто

@vsezabyto

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

24,852subscribers

-94 since we began measuring on 5 August 2026

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

Register entry

Telegram ID-1001192734079
TypeChannel
Username@vsezabyto
Created19 August 2020 — measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded6 August 2026
Last confirmed live8 November 2026
Measurements held57
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/vsezabyto

Topic

Memes & entertainment — 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 65% 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

24,82025,02924,924.55 August 2026 — 24,946 subscribers6 August 2026 — 24,946 subscribers6 August 2026 — 24,941 subscribers7 August 2026 — 24,938 subscribers9 August 2026 — 24,931 subscribers10 August 2026 — 24,919 subscribers11 August 2026 — 24,911 subscribers12 August 2026 — 24,904 subscribers13 August 2026 — 24,891 subscribers14 August 2026 — 24,885 subscribers16 August 2026 — 24,974 subscribers17 August 2026 — 24,986 subscribers18 August 2026 — 24,991 subscribers21 August 2026 — 24,993 subscribers23 August 2026 — 24,985 subscribers25 August 2026 — 24,993 subscribers26 August 2026 — 24,987 subscribers27 August 2026 — 24,990 subscribers28 August 2026 — 24,998 subscribers30 August 2026 — 25,000 subscribers31 August 2026 — 24,998 subscribers1 September 2026 — 24,997 subscribers2 September 2026 — 24,998 subscribers4 September 2026 — 24,992 subscribers6 September 2026 — 24,985 subscribers10 September 2026 — 24,975 subscribers12 September 2026 — 24,968 subscribers14 September 2026 — 24,957 subscribers15 September 2026 — 25,022 subscribers17 September 2026 — 25,029 subscribers27 September 2026 — 24,968 subscribers4 October 2026 — 24,942 subscribers9 October 2026 — 24,970 subscribers13 October 2026 — 24,958 subscribers14 October 2026 — 24,939 subscribers15 October 2026 — 24,927 subscribers17 October 2026 — 24,923 subscribers18 October 2026 — 24,918 subscribers19 October 2026 — 24,909 subscribers20 October 2026 — 24,876 subscribers21 October 2026 — 24,861 subscribers23 October 2026 — 24,860 subscribers24 October 2026 — 24,859 subscribers25 October 2026 — 24,854 subscribers26 October 2026 — 24,833 subscribers27 October 2026 — 24,843 subscribers28 October 2026 — 24,844 subscribers29 October 2026 — 24,841 subscribers30 October 2026 — 24,840 subscribers31 October 2026 — 24,839 subscribers1 November 2026 — 24,836 subscribers2 November 2026 — 24,833 subscribers3 November 2026 — 24,832 subscribers4 November 2026 — 24,821 subscribers6 November 2026 — 24,820 subscribers7 November 2026 — 24,822 subscribers8 November 2026 — 24,852 subscribers24,8525 August 20268 November 2026
57 measurements spanning 94 days, net -94. 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 24,789–25,060 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 57
Measured (UTC)SubscribersChange
8 Nov 2026, 08:5824,852+30
7 Nov 2026, 00:3924,822+2
6 Nov 2026, 01:5124,820-1
4 Nov 2026, 22:4124,821-11
3 Nov 2026, 20:5624,832-1
2 Nov 2026, 23:1824,833-3
1 Nov 2026, 21:5424,836-3
31 Oct 2026, 00:1824,839-1
30 Oct 2026, 00:2024,840-1
29 Oct 2026, 02:4824,841-3
28 Oct 2026, 04:0024,844+1
27 Oct 2026, 06:3824,843+10
26 Oct 2026, 08:1924,833-21
25 Oct 2026, 06:5624,854-5
24 Oct 2026, 08:2624,859-1
23 Oct 2026, 09:5024,860-1
21 Oct 2026, 06:3924,861-15
20 Oct 2026, 03:3624,876-33
19 Oct 2026, 02:3624,909-9
18 Oct 2026, 01:2624,918first reading

Engagement

33 posts held, back to 1 February 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 131 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
108.4%
avg views ÷ 24,852 subscribers
Avg views / post
26,900
5 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
5
of 33 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 6 November 2026
Posts held33 (1 February 2026 – 6 November 2026)
Views total134,700
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 02:44 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

Telegram’s own ‘edited’ marker: 0 of 5 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).

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

Mentions

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

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

“Забыто” (@vsezabyto), 24,852 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/vsezabyto.

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.