Telegram RegisterThe public register of Telegram
Telegram profile photo for GRAM MENFESS 💎

Channel

GRAM MENFESS 💎

@grammenfess

On this record: Topic · Previous handles · Observations · Channels linked by matching posts · Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

13,715subscribers

+7,845 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-1003614448116
TypeChannel
Username@grammenfess
CreatedBetween 1 December 2025 and 31 May 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live11 November 2026
Measurements held42
Confirmed unchanged1 time, most recently 11 November 2026
On Telegramt.me/grammenfess

Topic

Gambling & betting — 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 12 September 2026 and assigned it the closest of 31 fixed categories, at 79% 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.

Previous handles

@grammenfess was previously reachable at this handle, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.

@publikfess
held 5 November 2026 – 5 November 2026

Observations

These are measurements, not verdicts. Each one below states something we counted, alongside the evidence it was counted from, so you can check it rather than take it. None of them is graded: every observation this register holds is recorded at severity 0, because the precision of the detectors behind them has not been measured yet, and a rating we cannot support is worse than none. Read each as a fact about the data, not as a judgement about the channel. How we measure.

Content that also appears on other registered channels

Posts published here appear in near-verbatim form on 1 other registered channel. This entry also forms a group of 2 channels linked by matching posts. The matching is on the text itself, not on Telegram’s forward marker, so it finds a copy whether or not it was labelled as one.

Matching posts — open both and compare (5 of the pairs behind the counts below)
Posted firstThenOverlapGap
@grammenfess/52 · this entry9 Jul 2026, 11:20 UTC@JASTIPSAMUDERA/77169 Jul 2026, 11:20 UTC1.00under a minute
@grammenfess/56 · this entry10 Jul 2026, 09:35 UTC@JASTIPSAMUDERA/771710 Jul 2026, 09:35 UTC1.00under a minute
@grammenfess/62 · this entry19 Jul 2026, 20:27 UTC@JASTIPSAMUDERA/772219 Jul 2026, 20:27 UTC1.00under a minute
@JASTIPSAMUDERA/772628 Jul 2026, 12:25 UTC@grammenfess/64 · this entry28 Jul 2026, 12:26 UTC1.00under a minute
@grammenfess/66 · this entry1 Sept 2026, 07:40 UTC@JASTIPSAMUDERA/77331 Sept 2026, 07:40 UTC1.00under a minute
Channels this entry shares post bodies with, where at least one matching post pair has no forward credit between the two channels, or to a common source, recorded in our data
ChannelMatching postsText overlapTypical gapPublished first
@JASTIPSAMUDERA5 (5/5 hand-verifiable sample passed)1.00under a minutethis entry (3–2)

Text overlap is the Jaccard coefficient over the set of distinct three-word phrases in the two bodies: 1.00 is identical wording, and the threshold for counting a pair at all is 0.70. Candidates are generated by simhash LSH (4 x 16-bit bands, exact Hamming <= 3) verified against the bodies with Jaccard over the SET of distinct 3-word shingles. Published first counts which side of each matching pair carries the earlier timestamp — in this corpus, which is the limitation directly below.

What this cannot establish

MEASURED, DOMINANT ERROR SOURCE: a post ingested before 2026-08-06 may have carried a forward header that was not recorded. A 45-pair hand-check against live t.me pages found 14 (31%) where the live page shows a forward header naming the other channel and the database has none, plus 4 more (9%) naming a third party. The text match itself was wrong 0 times out of 45. Read attribution_capture.items_in_trusted_window before treating the unattributed count as a claim.

Telegram lets a channel forward a post with a header naming the source, and we only began reliably recording that header on 2026-08-06. 1 of the 2 matches recorded here fall after that date and carried no header when we read them. The rest predate reliable capture and are not evidence either way.

“Published first” means first in this corpus. We hold 21 comparable posts for this entry, running 29 June 2026 to 30 October 2026. A channel we have read one page deep will look younger than a neighbour we have read in full, and the order would flip with no change in the underlying facts.

The detector’s own notes on this observation, as it recorded them. Names in this_style are fields of the underlying evidence record, which the plain-English paragraphs above read out for this entry.

  • Verbatim republication has three causes and the text separates only two: a clone/mirror, unattributed copy-paste, or BOTH channels copying a common third source that neither attributes. The spread filter (content held by at most 8 channels) reduces the third and does not remove it.
  • 'Earliest' means earliest IN THIS CORPUS. A channel ingested one page deep will look younger than a neighbour ingested in full; corpus_coverage above is there to be checked before the direction is believed.
  • shared_verified_est extrapolates the sampled pass rate over the full narrow match count; sampled/passed are the numbers actually measured.
  • Absence of a forward header is not proof of intent: Telegram lets a channel disable forward attribution, and a credit written in the body is not parsed as attribution here (mention_edge_either_way above is the closest available signal).

Of the group of 2 channels, the one whose matching posts we hold earliest is @grammenfess — which is this entry. That is a statement about our reading window, not a claim of authorship.

Recorded under the key clone_mutual, last confirmed 11 November 2026. An observation that a later pass no longer finds is cleared, and a cleared observation is removed from this page rather than being shown struck through — we do not keep publishing a claim we have withdrawn. Dispute an observation.

Channels linked by matching posts

This channel is in a group of 2 registered channels linked by matching posts. Links are found by comparing text fingerprints across every channel on the register.

Which channel, if either, published first is deliberately not shown in this list. “First” could only mean first in our own crawl, which depends on how deep we happened to reach into each channel’s history, not on when the content was actually first posted. Our one hand-check read 45 of the highest-confidence flagged pairs against the live Telegram pages. In 18 of them the live page showed a “Forwarded from” credit that our database had no record of, so reading that pair as an unattributed copy was wrong; the check did not measure who published first. This list is ordered by subscriber count, the same as every other listing on this site, never by which channel we think came first. Near-verbatim matching has several ordinary explanations besides copying — a channel mirroring itself, an unattributed repost, or two channels independently repeating the same wire story — and this measurement cannot tell those apart. How this is measured.

Growth

5,84913,7159,7826 August 2026 — 5,870 subscribers6 August 2026 — 5,870 subscribers10 August 2026 — 5,854 subscribers13 August 2026 — 5,852 subscribers16 August 2026 — 5,853 subscribers20 August 2026 — 5,849 subscribers23 August 2026 — 5,859 subscribers26 August 2026 — 5,851 subscribers28 August 2026 — 5,860 subscribers4 September 2026 — 5,952 subscribers10 September 2026 — 6,013 subscribers13 September 2026 — 6,037 subscribers17 September 2026 — 6,102 subscribers26 September 2026 — 6,221 subscribers5 October 2026 — 6,427 subscribers12 October 2026 — 6,595 subscribers15 October 2026 — 6,650 subscribers17 October 2026 — 13,405 subscribers18 October 2026 — 13,417 subscribers19 October 2026 — 13,412 subscribers20 October 2026 — 13,424 subscribers21 October 2026 — 13,419 subscribers23 October 2026 — 13,409 subscribers24 October 2026 — 13,418 subscribers25 October 2026 — 13,413 subscribers26 October 2026 — 13,459 subscribers27 October 2026 — 13,480 subscribers28 October 2026 — 13,490 subscribers29 October 2026 — 13,516 subscribers30 October 2026 — 13,534 subscribers31 October 2026 — 13,538 subscribers31 October 2026 — 13,561 subscribers1 November 2026 — 13,559 subscribers2 November 2026 — 13,603 subscribers4 November 2026 — 13,604 subscribers4 November 2026 — 13,621 subscribers5 November 2026 — 7,233 subscribers5 November 2026 — 13,650 subscribers6 November 2026 — 13,653 subscribers8 November 2026 — 13,667 subscribers9 November 2026 — 13,696 subscribers11 November 2026 — 13,715 subscribers6 August 202611 November 2026
42 measurements spanning 97 days, net +7,845. 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 4,669–14,895 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 42
Measured (UTC)SubscribersChange
11 Nov 2026, 09:1913,715+19
9 Nov 2026, 17:1513,696+29
8 Nov 2026, 07:4613,667+14
6 Nov 2026, 23:2613,653+3
5 Nov 2026, 23:1813,650+6,417
5 Nov 2026, 12:227,233-6,388
4 Nov 2026, 23:4013,621+17
4 Nov 2026, 00:2013,604+1
2 Nov 2026, 23:0813,603+44
1 Nov 2026, 21:1513,559-2
31 Oct 2026, 23:4513,561+23
31 Oct 2026, 01:4113,538+4
30 Oct 2026, 03:0013,534+18
29 Oct 2026, 00:4713,516+26
28 Oct 2026, 02:1613,490+10
27 Oct 2026, 02:1813,480+21
26 Oct 2026, 05:1813,459+46
25 Oct 2026, 03:0613,413-5
24 Oct 2026, 00:2913,418+9
23 Oct 2026, 00:5713,409first reading

Engagement

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

ERR · 30 days
4.75%
avg views ÷ 13,715 subscribers
Avg views / post
652
7 posts measured
Reaction rate
—
this channel exposes no reaction counts
Posts in window
8
of 37 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 31 October 2026
Posts held37 (28 June 2026 – 31 October 2026)
Views total4,561
Reactions total—
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken5 Nov 2026, 12: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.

Reaction mix

17 reactions across 6 posts, in 3 distinct kinds. The most used accounts for 58.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤1058.8%
🥰529.4%
🔥211.8%

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

Measured over the 37 most recent posts we hold, published 28 June 2026 to 31 October 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

Telegram’s own ‘edited’ marker: 0 of 8 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).

31 Oct 2026, 07:47 UTC439 viewsread 5 November 2026
Photo

gift bear haloween 🧸 50 ⭐️ sudah bisa di beli dan bisa confess gift dibot/miniapp @starsfastbuy_bot!

31 Oct 2026, 03:08 UTC489 viewsread 5 November 2026

new gifts released 🧸 50⭐️ Beli stars 50 ⭐️ hanya 14.250 @starsfastbuy_bot

30 Oct 2026, 04:39 UTC530 viewsread 5 November 2026
Photo

sekarang sudah ada top stars 🏆 fitur ini akan menunjukan pembeli stars paling banyak di @starsfastbuy_bot akan ada hadiah menarik untuk peringkat 1-3 sampai waktu yang ditentukan 📌

29 Oct 2026, 03:30 UTC468 viewsread 5 November 2026

📣 Cek harga gift kalian jika di cv ke miniapp @starsfastbuy_bot kalau cocok dengan harga yg diberikan langsung pencet setuju ✅ dan chat gua ya @jhosua

27 Oct 2026, 11:44 UTC523 viewsread 5 November 2026
Photo

happy 1.000 orders @starsfastbuy_bot semoga kedepannya makin banyak orders, dan semakin sukses 🔥❤️

16 Oct 2026, 17:11 UTC≈1,430 viewsread 5 November 2026
Photo

📣 buat kalian yang mau cv gift to idr ‼️ cek harga gift kamu jika di cv di miniapp @starsfastbuy_bot jika setuju, klik setuju ✅ lalu chat saya @jhosua

12 Oct 2026, 04:23 UTC≈1,010 viewsread 5 November 2026

📣 Cek harga gift kalian jika di cv ke miniapp @starsfastbuy_bot kalau cocok dengan harga yg diberikan langsung pencet setuju ✅ dan chat gua ya @jhosua

7 Oct 2026, 16:51 UTC≈1,090 viewsread 5 November 2026

Jangan lupa mainin miniapp di @starsfastbuy_bot dan dapatkan diamond 💎 yang bisa ditukar menjadi uang 💵 bot auto buy @starsfastbuy_bot 50 ⭐️ hanya 14.250 bisa confess gift ke pacar/hts/temen/mantan/keluarga kamu

3 Oct 2026, 16:23 UTC≈1,120 viewsread 5 November 2026

🎉 GIVEAWAY #4950 ENDED ━━━━━━━━━━━━━━ 📢 Channel : @dagetele, @lpmbagidana, @sailxor, @grammenfess ☎️ Claim : @jhosua 🏆 Pemenang : • saldo 1.000 : @shoowoff • saldo 1.000 : @oCuanki • saldo 1.000 : @kuevuhoki • 500p : @adellysium • 500p : @Bratun • 500p : @WonHaneuln • 500p : @gayyal • 500p : @daraOt • 500p : @stroberihoki • 500p : @senavndu ━━━━━━━━━━━━━━ 👥 Total Peserta: 164

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

“GRAM MENFESS 💎” (@grammenfess), 13,715 subscribers as measured 11 November 2026. Telegram Register, tgregister.com/channel/publikfess.

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.