Telegram RegisterThe public register of Telegram
Telegram profile photo for BadFess Time

Channel

BadFess Time

@Badfess

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

11,321subscribers

-685 since we began measuring on 8 August 2026

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

Register entry

Telegram ID-1001781750798
TypeChannel
Username@Badfess
CreatedBetween 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded8 August 2026
Last confirmed live25 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 25 September 2026
On Telegramt.me/Badfess

Topic

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 73% 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 why it has no browse page of its own yet.

Growth

11,32112,00611,663.58 August 2026 — 12,006 subscribers8 August 2026 — 12,006 subscribers9 August 2026 — 11,995 subscribers10 August 2026 — 11,974 subscribers11 August 2026 — 11,952 subscribers12 August 2026 — 11,937 subscribers13 August 2026 — 11,919 subscribers14 August 2026 — 11,900 subscribers16 August 2026 — 11,884 subscribers17 August 2026 — 11,837 subscribers18 August 2026 — 11,813 subscribers19 August 2026 — 11,794 subscribers20 August 2026 — 11,786 subscribers21 August 2026 — 11,766 subscribers23 August 2026 — 11,739 subscribers25 August 2026 — 11,713 subscribers26 August 2026 — 11,689 subscribers27 August 2026 — 11,675 subscribers28 August 2026 — 11,658 subscribers29 August 2026 — 11,648 subscribers30 August 2026 — 11,633 subscribers31 August 2026 — 11,617 subscribers1 September 2026 — 11,606 subscribers2 September 2026 — 11,595 subscribers3 September 2026 — 11,586 subscribers5 September 2026 — 11,557 subscribers8 September 2026 — 11,509 subscribers11 September 2026 — 11,468 subscribers13 September 2026 — 11,443 subscribers14 September 2026 — 11,419 subscribers16 September 2026 — 11,405 subscribers18 September 2026 — 11,386 subscribers25 September 2026 — 11,321 subscribers8 August 202625 September 2026
33 measurements spanning 48 days, net -685. 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 11,218–12,109 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
25 Sept 2026, 11:2211,321-65
18 Sept 2026, 22:2011,386-19
16 Sept 2026, 12:0111,405-14
14 Sept 2026, 18:5511,419-24
13 Sept 2026, 03:3611,443-25
11 Sept 2026, 08:0111,468-41
8 Sept 2026, 10:1511,509-48
5 Sept 2026, 07:1811,557-29
3 Sept 2026, 09:5611,586-9
2 Sept 2026, 05:2811,595-11
1 Sept 2026, 05:0911,606-11
31 Aug 2026, 01:5711,617-16
30 Aug 2026, 03:1911,633-15
29 Aug 2026, 01:5811,648-10
28 Aug 2026, 05:1911,658-17
27 Aug 2026, 02:0711,675-14
26 Aug 2026, 01:3311,689-24
25 Aug 2026, 00:3611,713-26
23 Aug 2026, 12:2811,739-27
21 Aug 2026, 20:3811,766first reading

Engagement

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

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 20 posts for this entry, the most recent from 26 May 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

331 reactions across 10 posts, in 8 distinct kinds. The most used accounts for 34.4% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🔥11434.4%
🤣8525.7%
🤡5316.0%
💯319.37%
❤‍🔥216.34%
❤175.14%
👏72.11%
🙊30.906%

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 11 of the 20 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 331 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 20 most recent posts we hold, published 26 May 2026 to 26 May 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.

Recent posts

26 May 2026, 13:26 UTC≈5,820 views111 reactionsread 3 September 2026

#WH Close. Thanks yang udah mangkal dimari, besok besok lu semua sabi dah mangkal.

🤣71🤡20❤‍🔥13🔥7

26 May 2026, 13:23 UTC≈5,890 views119 reactionsread 3 September 2026

#Julid PLS YA ANJING HOMOPHOBIC ITU GANGGU BANGET

🔥64🤡29🤣14💯9🙊3

26 May 2026, 13:19 UTC≈5,690 views23 reactionsread 3 September 2026

#Julid badfess gini aja ya, gua lebih suka yang barbar gini tanpa mendem

💯22❤1

26 May 2026, 13:18 UTC≈5,550 views44 reactionsread 3 September 2026

#Julid homophobic mah homophobic aje jangan beralibi "tuh muse masih minor" apaan dah blok, kalau homophobic gausah main rp kata gua mah

🔥40🤡4

26 May 2026, 13:14 UTC≈5,210 views10 reactionsread 3 September 2026

#Julid base L biru subsnya mayan tapi commentny flop kalau lgi pinned Jb, Emang jir, pernah lihat udah puluhan menit komennya masih dikit, jujur kasian 😭

❤‍🔥8❤2

26 May 2026, 13:11 UTC≈4,940 views3 reactionsread 3 September 2026

#Julid anak rp zaman skrg baperan, bawa bawa rl, tg di viralin, hdh mls bgt gerak dikit salah anjr wkwk

❤3

26 May 2026, 13:10 UTC≈4,710 views0 reactionsread 3 September 2026

#Julid aneh.. cuman bilang gini “ aku mau stay nondate aja ah GKMAU PUNYA FWA/PARTNER 72h JUGAA, mau stay single aja.. tangki cintaku udah penuh dari papi sama abang “ aja sender langsung dikata incest sama papi & abang wehhh 🤣🤣👈🏻👈🏻 konyol ya.. padahal kan emang btul cinta nan kasih sayangku udah penuh, emang salah ya klo mau stay nondate¿?

26 May 2026, 13:10 UTC≈4,220 viewsread 3 September 2026

#Julidhttps://t.me/Badfess/144322?comment=4455222 ss, mereka alasan nya gabisa ngimbangin effort gua 🥹 emang salah ya effort ke pasangan?

26 May 2026, 13:10 UTC≈3,860 viewsread 3 September 2026

#Julid base L biru subsnya mayan tapi commentny flop kalau lgi pinned

26 May 2026, 13:10 UTC≈3,730 views9 reactionsread 3 September 2026

#Julid ga sopan tau nungguin putusnya hubungan orang

❤9

Showing the 12 most recent of 20 posts we hold for @Badfess. 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 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 25 September 2026 — this entry's latest reading, not the date you are reading this.

“BadFess Time” (@Badfess), 11,321 subscribers as measured 25 September 2026. Telegram Register, tgregister.com/channel/Badfess.

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.