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 11 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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
62 measurements spanning 91 days, net +2,327. 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,131–15,156 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 62
Measured (UTC)
Subscribers
Change
5 Nov 2026, 16:39
14,807
+25
4 Nov 2026, 14:16
14,782
+38
3 Nov 2026, 11:18
14,744
+49
2 Nov 2026, 13:44
14,695
+18
1 Nov 2026, 10:26
14,677
+10
31 Oct 2026, 11:35
14,667
-3
30 Oct 2026, 12:08
14,670
+16
29 Oct 2026, 14:11
14,654
-5
28 Oct 2026, 14:17
14,659
+24
27 Oct 2026, 14:50
14,635
+8
26 Oct 2026, 16:17
14,627
+15
25 Oct 2026, 19:10
14,612
+42
24 Oct 2026, 16:16
14,570
+6
22 Oct 2026, 15:08
14,564
+15
21 Oct 2026, 09:49
14,549
+20
20 Oct 2026, 10:09
14,529
+16
19 Oct 2026, 12:58
14,513
+19
18 Oct 2026, 11:56
14,494
+26
17 Oct 2026, 09:46
14,468
-15
16 Oct 2026, 08:40
14,483
first reading
Engagement
1,027 posts held, back to 6 August 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 55 pages of Telegram’s post history, 20 posts per page.
ERR · 30 days
1.23%
avg views ÷ 14,807 subscribers
Avg views / post
182
93 posts measured
Reaction rate
0.693%
reactions ÷ views · ER floor
Posts in window
93
of 1,027 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. It is computed over the 8 of 93 measured posts that carry a reaction reading, and over those same posts' views.
What these figures were computed from
Window
Rolling 30 days · latest post in window 5 November 2026
Posts held
1,027 (6 August 2026 – 5 November 2026)
Views total
16,913
Reactions total
15
Forwards / comments
not exposed by the public surface — not measured, not estimated
Readings taken
6 Nov 2026, 05:42 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.
What this channel posts
Photos
≈72,000
Videos
≈595
Links
≈40,000
Lifetime counters from Telegram’s own channel header, read 6 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.
Video runtime
46s
Average length
8s
Measured directly from 6 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
Reaction mix
472 reactions across 117 posts, in 24 distinct kinds. The most used accounts for 29.0% of them.
Every reaction kind recorded on the sample, most used first
Reaction
Count
Share
Share, drawn
😨
137
29.0%
❤
88
18.6%
💔
60
12.7%
👀
32
6.78%
🤩
26
5.51%
🔥
18
3.81%
💘
16
3.39%
😴
16
3.39%
🎉
14
2.97%
💋
12
2.54%
🏆
10
2.12%
🌚
8
1.69%
🕊
5
1.06%
🎄
4
0.847%
👍
4
0.847%
🙏
4
0.847%
🆒
3
0.636%
🍓
3
0.636%
💊
3
0.636%
❤🔥
2
0.424%
4 further kinds
7
1.48%
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 128 of the 1,000 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 472 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 7 August 2026 to 5 November 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.
Advertising
Ad load
0.4%
4 of 1,000 posts carry an ad marker
Regulatory tokens
0
none — marked by hashtag only
Median views · ads
213
over 4 measured posts
Median views · rest
94.0
over 996 measured posts
An ad marker, not a judgement about a post. A post is counted here because it carries one of two explicit markings: an erid token, which Russian law has required on paid placements since 2022 and which is issued against a specific advertising contract, or a #реклама / #ad hashtag in the body, which is the channel declaring it itself. The first is documentary; the second is a self-declaration and is weaker. No classifier reads the text and decides — nothing on this site guesses that a post is an advertisement.
This is a floor, and it can only ever be a floor. A channel that runs paid placements without marking them produces no marker for us to count, and an unmarked ad is indistinguishable from an ordinary post on the public surface. The ad load above therefore means “the share of posts that declared themselves”, never “the share of posts that were paid for”. A low figure is not evidence of a channel that runs few ads.
Both figures are medians, and no ratio between them is published. Each is a view reading that actually occurred on a post, picked by percentile_disc rather than averaged, so one viral post cannot move it and no interpolated value is invented between two readings. The sample on one side is under five posts, which is too thin to compare. The two figures are shown side by side with the count behind each, and deliberately not divided into a headline like “ads get x% fewer views” — an arithmetic that is easy to print and, at this sample size, means nothing.
Measured over the 1,000 most recent posts we hold (the sample is capped at 1,000), published 7 August 2026 to 5 November 2026. Views are the latest single reading held for each post, and any reading at or above 1,000 is rounded by Telegram to three significant figures.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 93 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).
мне возможно дадут пизды за этот пост нооо
ищу вз пдп (сабаюсь с твинка), мнение и опрос
в опросе тапайте за инно
во мнении пишите, что я ирл каору нагиса и чо-нидь от себя если хотите
УТОЧНЯЙТЕ СРАЗУ ЧТО ТАПАТЬ ВАМ ПЖ
длиннющие копипасты ИГНОРИРУЮ!!!!
@kaworuIover @kaworuIover @kaworuIover
╰► ♡ @InfocfNBot <> | #адмтейк
привет. ищу вз: пм, рк, мнение.
в мнении что я тру жена италии
вместо перечисленного могу что то тапнуть, если у вас нету этого
@FelicianoVargaswife_info
╰► ♡ @InfocfNBot < 🎀 > | #тейк
͡ . ⌒⌒ ㅤhi !ㅤ‿
ищу вз на все !! ღ в опросе тапать friend / fan
. а в мнении писать — ирл *и кто нибудь из моего кинн листа* ! так же прошу добавить что то от себя
. ⁝ @Madeleneirl
╰► ♡ @InfocfNBot < 🎀 > | #тейк
Showing the 12 most recent of 1,027 posts we hold for @INFOCONFESSION1. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republished by 51 registered channels. The 48 listed are the ones that have forwarded the most posts; the rest are counted here but not each listed.
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 46 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 23 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
Handles this channel named that no longer answer
Dead references
51
handles named in this channel’s posts, vacant today
Evidenced gone
49
we ourselves saw one of these resolve, at some point
Never seen alive
2
vacant every time we have ever looked
@INFOCONFESSION1 named 51 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all. A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Evidenced gone
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
@minatoarisatokisser named in 2 posts, 9 August 2026 – 3 September 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@tevroinf named in 2 posts, 2 September 2026 – 2 September 2026 · confirmed gone 24 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@infonanacute named in 2 posts, 8 August 2026 – 9 August 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@kefainfo named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@tsumurikiss named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mako_reiz3i named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@greybunnyfrvr named in 1 post, 3 September 2026 – 3 September 2026 · confirmed gone 23 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@vivein_in named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@chenyyayaah named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 6 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@lolocuteirl named in 1 post, 2 September 2026 – 2 September 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@pjhxeifhiw named in 1 post, 29 August 2026 – 29 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@aishiteruforeverr named in 1 post, 29 August 2026 – 29 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@kasverr named in 1 post, 29 August 2026 – 29 August 2026 · confirmed gone 12 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@lcconf named in 1 post, 21 August 2026 – 21 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@jwjwwes named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@keoheaven named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 30 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@anjocoded named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 14 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@ozon_3aka3 named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@novasweetie named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 17 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mewsyash named in 1 post, 16 August 2026 – 16 August 2026 · confirmed gone 11 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@infomeetcf named in 1 post, 15 August 2026 – 15 August 2026 · confirmed gone 29 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@itz_skeetinfo named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 15 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@cherbyachkerr666okmgovno named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 21 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@flixxkiss named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@leroybonbon named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@marlowwwkinnie named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mixxtws named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@sayrinainfo named in 1 post, 9 August 2026 – 9 August 2026 · confirmed gone 30 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@tsukichaninfo named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 13 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@inf0l8 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@manno_sun named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 29 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@alwixxcute named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 31 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@inf0_loveletter named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hellocharlotteeel named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@vanillainfolove67 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@mleegh named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 5 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@hellchik_info named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 29 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@outsiderskisser named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 16 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@gfritsu named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 25 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@pinkzhenya named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@cutie4so named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 30 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@rionirlest named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@akechichan named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 3 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@scenee_queen named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 1 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@sweetisp2 named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 27 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@blshinfo named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 26 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@a1ng3ell named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@infoyuqii named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 4 November 2026 (two independent sightings — see how we confirm a dead handle)evidenced
@kwndeinfo named in 1 post, 8 August 2026 – 8 August 2026 · confirmed gone 26 October 2026 (two independent sightings — see how we confirm a dead handle)evidenced
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
@tgconfessionn named in 1 post, 4 November 2026 – 4 November 2026
1 more handle is in this same list but not shown individually here — capped at 50.
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 5 November 2026 — this
entry's latest reading, not the date you are reading this.
“INFO CONFESSION” (@INFOCONFESSION1), 14,807 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/INFOCONFESSION1.
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.