Telegram RegisterThe public register of Telegram
Telegram profile photo for 𝗠𝗮𝗿𝗹𝗯𝗼𝗿𝗼𝗡𝗙𝗧

Channel

𝗠𝗮𝗿𝗹𝗯𝗼𝗿𝗼𝗡𝗙𝗧

@MarlboroGift

On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Posts edited after publishing · Posts recorded as deleted · Polls · Citations · Handles named that no longer answer · Cite this entry

16,773subscribers

+1,983 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002177807776
TypeChannel
Username@MarlboroGift
CreatedBetween 1 June 2024 and 30 September 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live8 November 2026
Measurements held61
Confirmed unchanged1 time, most recently 8 November 2026
On Telegramt.me/MarlboroGift

Topic

Crypto & trading — 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 71% 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

14,30818,67716,492.516,7737 August 20268 November 2026
61 measurements spanning 93 days, net +1,983. 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 13,653–19,332 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 61
Measured (UTC)SubscribersChange
8 Nov 2026, 08:0116,773-8
7 Nov 2026, 00:2616,781+18
6 Nov 2026, 01:0516,763-20
4 Nov 2026, 23:4716,783-4
3 Nov 2026, 23:3916,787+6
2 Nov 2026, 20:0816,781+8
1 Nov 2026, 21:4016,773-1,904
31 Oct 2026, 18:4018,677+2,037
30 Oct 2026, 20:3516,640-25
29 Oct 2026, 22:4616,665-24
29 Oct 2026, 01:1716,689-19
28 Oct 2026, 00:5516,708-23
27 Oct 2026, 00:0916,731-16
26 Oct 2026, 02:2916,747+1,409
25 Oct 2026, 01:3715,338-23
24 Oct 2026, 04:4615,361+10
23 Oct 2026, 06:0715,351+333
22 Oct 2026, 07:0915,018+361
21 Oct 2026, 02:0914,657-37
19 Oct 2026, 20:5914,694first reading

Engagement

876 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 65 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
3.77%
avg views ÷ 16,773 subscribers
Avg views / post
633
190 posts measured
Reaction rate
5.42%
reactions ÷ views · ER floor
Posts in window
190
of 876 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 188 of 190 measured posts that carry a reaction reading, and over those same posts' views.

What these figures were computed from
WindowRolling 30 days · latest post in window 7 November 2026
Posts held876 (6 August 2026 – 7 November 2026)
Views total120,225
Reactions total6,481
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Nov 2026, 04: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

Video runtime
10m 06s
Average length
26s

Measured directly from 23 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

27,179 reactions across 860 posts, in 53 distinct kinds. The most used accounts for 14.8% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 60351747216271028594,02014.8%
custom 60331087736382496043,80414.0%
custom 60351259007338483012,6639.80%
🍾2,0497.54%
❤1,9427.15%
custom 59384600038106800221,4605.37%
custom 60348496613222720711,3214.86%
custom 59385202235471367811,1414.20%
custom 59361416835435141908613.17%
custom 60349618329831416157922.91%
💋7562.78%
🤣6282.31%
custom 60327369840892402865992.20%
🍓5341.96%
🔥4921.81%
custom 53076023009975034984701.73%
custom 59111053270376888753931.45%
custom 60353072514329551413521.30%
custom 58639618547363410583201.18%
custom 59383906057291117152921.07%
33 further kinds2,2908.43%

Custom emoji. 14 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.

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 863 of the 876 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 27,179 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 876 most recent posts we hold, published 6 August 2026 to 7 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.

Telegram Stars

Stars received
51,929
across the posts below
Posts paid on
306
of 875 we hold a reading for · 35%
Most on one post
8,630
single highest reading

A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @MarlboroGift. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.

Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.

This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.

Counted over the 876 most recent posts we hold for this entry, published 6 August 2026 to 7 November 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.

Recent posts

Telegram’s own ‘edited’ marker: 15 of 190 posts held from the last 30 days (7.89%) 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).

7 Nov 2026, 21:10 UTC468 views18 reactionsread 8 November 2026

عه😳

custom 593846000381068002212❤‍🔥3custom 58639618547363410583

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 21:07 UTC500 views22 reactionsread 8 November 2026

چکار داری میکنی؟🚬

❤‍🔥12custom 58639618547363410585custom 59384600038106800224custom 59543070802182218571

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:13 UTC680 views38 reactions1 Starread 8 November 2026
Photo

برکت❤️

custom 593852022354713678115🍓6custom 59384600038106800225💋3custom 58639618547363410583custom 59988095041148104153custom 59361416835435141902custom 60331087736382496041

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:11 UTC654 views22 reactionsread 8 November 2026

پنجمین کامنت ارسال این ایموجی👀

❤‍🔥8custom 58639618547363410585custom 59384600038106800225custom 60329161142902565952custom 59385202235471367811custom 60331087736382496041

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:10 UTC627 views15 reactionsread 8 November 2026

سومین کامنت ارسال این ایموجی🔥

❤‍🔥7custom 58639618547363410584custom 59384600038106800224

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:09 UTC647 views26 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی👑

❤‍🔥12custom 58639618547363410587custom 59384600038106800227

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:08 UTC636 views33 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی😎

custom 593846000381068002216❤‍🔥9custom 58639618547363410588

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:08 UTC616 views24 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی❤️

custom 603310877363824960410❤‍🔥6custom 59384600038106800226custom 58639618547363410581custom 59385202235471367811

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:07 UTC635 views35 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی❤️‍🔥

custom 593852022354713678114custom 60331087736382496048custom 59361416835435141906❤‍🔥2custom 58639618547363410582custom 59384600038106800222🍾1

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:06 UTC611 views35 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی👑

custom 593852022354713678118🍾6custom 59384600038106800226custom 58639618547363410582custom 59361416835435141902❤‍🔥1

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:05 UTC613 views29 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی🐉

custom 593852022354713678114custom 59384600038106800228custom 59361416835435141905❤‍🔥1custom 58639618547363410581

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

7 Nov 2026, 20:04 UTC634 views22 reactionsread 8 November 2026

اولین کامنت ارسال این ایموجی🎭

custom 593852022354713678110custom 59384600038106800225custom 60331087736382496045❤‍🔥1custom 58639618547363410581

Signed 𝐌𝐚𝐫𝐥𝐛𝐨𝐫𝐨 @𝐭𝐨𝐨𝐟𝐚𝐧𝐢

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

Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.

Posts edited after publishing

@MarlboroGift edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.

An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.

First edit seen
9 August 2026
Most recent edit
9 August 2026

Posts recorded as deleted after publishing

We recorded 3 posts on @MarlboroGift as deleted — posts this register held that were missing from the channel’s public page on two separate reads, taken from different network addresses at least an hour apart.

A deletion is not wrongdoing. This register can see that a post it held is no longer on the channel’s public page, and when — not why. Expired ad placements, reposts, rotating links and corrections all look the same. This is a count of recorded detections, not an exact total: it misses deletions we could not see, because only a post we held and later re-read inside the page can be seen to go, and it may include a small number of wrong records. How this is measured.

First seen missing
8 August 2026
Most recent seen missing
2 September 2026
Median time before seen missing
15 hours
Seen missing in the last 30 days
0

Polls

The poll we hold for this entry, as Telegram rendered it when we read the post. A poll’s figures keep moving after that, so each one is dated.

11 Aug 2026, 18:31 UTCAnonymous Poll199 voters

🤯بنظر شما باتوجه به انتشاره این خبر،روزه تولده تلگرام پاول چیکار قراره بکنه؟🤯

  1. تدی میده بیرون مخصوص تولد تلگرام🥵45%
  2. گیفت جدید با ساپلای محدود میده بیرون🔥29%
  3. آپگرید چنتا گیفتو میده بیرون🤯41%
  4. هیچ کاری نمیکنه🛡28%

The shares total 143%, above 100: this poll accepts more than one answer per voter. No per-option vote count is published, so the number of voters who chose each option is not derivable and is not shown.

Percentages only — there are no per-option vote counts here, because Telegram publishes none. The public post preview gives each option’s share and a single voter total, and nothing else. Multiplying one by the other would produce a per-option tally that looks measured and is not: the shares are rounded to whole numbers before we ever see them. We print what was published and leave the column that does not exist empty.

The shares need not add up to 100. Rounding alone puts many polls at 99 or 101. A poll that allows more than one answer per voter runs well past 100 by design, and several here do. The bars are drawn against a fixed 100% track at each option’s own percentage rather than normalised to the total, so a poll that exceeds it shows that it does instead of being quietly rescaled.

Read from the 876 most recent posts we hold, published 6 August 2026 to 7 November 2026. Telegram labels each poll by kind — an anonymous poll, a quiz, a closed set of final results — and that label is reproduced rather than paraphrased.

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

“𝗠𝗮𝗿𝗹𝗯𝗼𝗿𝗼𝗡𝗙𝗧” (@MarlboroGift), 16,773 subscribers as measured 8 November 2026. Telegram Register, tgregister.com/channel/MarlboroGift.

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.