Telegram RegisterThe public register of Telegram
Telegram profile photo for Tặng momo 50k

Channel

Tặng momo 50k

@momo50k

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

4,029subscribers

-116 since we began measuring on 7 August 2026

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

Register entry

Telegram ID-1002268082410
TypeChannel
Username@momo50k
Created13 October 2024measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live24 August 2026
Measurements held8
Confirmed unchanged1 time, most recently 24 August 2026
On Telegramt.me/momo50k

Growth

4,0294,1454,0877 August 2026 — 4,145 subscribers7 August 2026 — 4,145 subscribers8 August 2026 — 4,140 subscribers11 August 2026 — 4,118 subscribers14 August 2026 — 4,100 subscribers17 August 2026 — 4,081 subscribers21 August 2026 — 4,061 subscribers24 August 2026 — 4,029 subscribers7 August 202624 August 2026
8 measurements spanning 17 days, net -116. 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,012–4,162 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
24 Aug 2026, 16:574,029-32
21 Aug 2026, 00:534,061-20
17 Aug 2026, 20:444,081-19
14 Aug 2026, 20:444,100-18
11 Aug 2026, 09:444,118-22
8 Aug 2026, 08:004,140-5
7 Aug 2026, 14:024,145no change
7 Aug 2026, 13:524,145first reading

Engagement

2 posts held, back to 13 October 2024the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 5 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
0.099%
avg views ÷ 4,029 subscribers
Avg views / post
4.0
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 2 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 7 August 2026
Posts held2 (13 October 20247 August 2026)
Views total4
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken8 Aug 2026, 12:16 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

7 Aug 2026, 17:14 UTC4 viewsread 8 August 2026
Forwarded from @km118kPhoto

Game Mới Ra Tặng 188k cho tân thủ 𝐍𝐇Ậ𝐍 188𝐊 𝐗 𝟏 𝐕Ò𝐍𝐆 𝐂ƯỢ𝐂 ✅Link đăng ký: https://www.blackgoldvn.com?fid=44150587 ✅Các bước nhận code: Bước 1: Tải app Bước 2: Liên kết sdt Bước 3: Chơi x1 vòng cược 👉Min rút: 300k Lưu ý phải liên kết số điện thoại và ngân hàng rồi mới được chơi Chơi 1 vòng cược vào làm lệnh rút tiền, ko cần nạp

Showing the 2 most recent of 2 posts we hold for @momo50k. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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.

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

“Tặng momo 50k” (@momo50k), 4,029 subscribers as measured 24 August 2026. Telegram Register, tgregister.com/channel/momo50k.

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.