Telegram RegisterThe public register of Telegram
Telegram profile photo for ALYNTHUM

Channel

ALYNTHUM

@Alynthum

On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry

6,747subscribers

+26 since we began measuring on 14 August 2026

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

Register entry

Telegram ID-1002180538553
TypeChannel
Username@Alynthum
CreatedBetween 1 June 2024 and 30 September 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 August 2026
Last confirmed live27 August 2026
Measurements held7
Confirmed unchanged1 time, most recently 27 August 2026
On Telegramt.me/Alynthum

Growth

6,7206,7506,73514 August 2026 — 6,721 subscribers14 August 2026 — 6,721 subscribers15 August 2026 — 6,720 subscribers18 August 2026 — 6,735 subscribers21 August 2026 — 6,750 subscribers25 August 2026 — 6,743 subscribers27 August 2026 — 6,747 subscribers6,74714 August 202627 August 2026
7 measurements spanning 14 days, net +26. 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 6,716–6,755 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
27 Aug 2026, 21:456,747+4
25 Aug 2026, 04:256,743-7
21 Aug 2026, 23:486,750+15
18 Aug 2026, 09:186,735+15
15 Aug 2026, 04:456,720-1
14 Aug 2026, 08:006,721no change
14 Aug 2026, 07:496,721first reading

Engagement

60 posts held, back to 13 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 3 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
1.72%
avg views ÷ 6,747 subscribers
Avg views / post
116
57 posts measured
Reaction rate
4.92%
reactions ÷ views · ER floor
Posts in window
60
of 60 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 12 of 57 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 20 August 2026
Posts held60 (13 August 202620 August 2026)
Views total6,623
Reactions total70
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken20 Aug 2026, 05:06 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
1m 37s
Average length
19s

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

70 reactions across 12 posts, in 8 distinct kinds. The most used accounts for 32.9% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
😢2332.9%
😭2231.4%
1014.3%
🔥710.0%
🥰34.29%
👀22.86%
💘22.86%
🕊11.43%

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

Measured over the 60 most recent posts we hold, published 13 August 2026 to 20 August 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

20 Aug 2026, 02:05 UTC90 viewsread 20 August 2026
Photo

*omg* time flies so fast. it looks like this is the end of my working shift. i'm #jongwoo 🍁 offer a closing message for you. ˚.⏰ ᵎᵎ i'm glad you all spend time with me during my shift, it was really fun. we'll meet again & i promise will bring more candy for hummies⭑.ᐟ 🎨🫟 ۫ 𐑺 i give a fun place to play at @hummies or @subalynthum, we usually do fun game & chit chat. don't forget to stop by @ConiumPub, i'll be waiti

20 Aug 2026, 02:05 UTC83 viewsread 20 August 2026

🍀 temenan ma orang, yang satu dunianya udah pacarnya doang sampe temennya ga dianggep semua, intinya pacarnya diatas segalanya. yang satu dateng kalau lagi berantem sama pacarnya + berantem sama cc barunya. giliran saya ngejauh dr mereka, mereka malah bilang saya ga tulus temenan sama mereka lagi (jujur capek) akhirnya saya pindah akun tanpa ajak mereka, eh mereka ngambek soalnya saya slr in mulu.

20 Aug 2026, 02:03 UTC82 viewsread 20 August 2026

🍀 bete deh sama temen yang on sp terus tapi chat sender dari sebulan lalu egk dibalas. sender udah rechat, tapi tetep aja tuh gada balasan. padahal utu obrolan mau ngajakin temp bareng, dari dulu bilang mau temp tapi ga jadi jadi... bagusnya gimana ya mies? apa dia udah ga mau berteman sama sender lagi huft 😢😢

20 Aug 2026, 01:57 UTC89 viewsread 20 August 2026

🍀 emg rawan yak temenan stuck di perkenalan yak... baru ngenalin diri eh udah di cuekin berhari-hari. ngapaa ya? apkh sender egk menarik? apkh mereka egk tertarik? padahal sender fast respon kalau pegang hp & tipe yang sik asik alay. limited edition pokoknya

20 Aug 2026, 01:54 UTC109 viewsread 20 August 2026

CW // SLIGHT NSFW ON AVA Happe birthday to Mikey and all Mikey portrayers 🎉🎉 esp bang @brionees, semua alynthum ditraktir taiyaki katanya 🤩

20 Aug 2026, 01:48 UTC91 viewsread 20 August 2026
Video

🍀. waduch waduch slmt pagi smuanyahh 😍🥰🌹🌹🌹🌹🌹 #sEmAngatSehat #zoNaWakAnda

20 Aug 2026, 01:48 UTC82 views2 reactionsread 20 August 2026
Video

minggir mies minggir, ketua himpunan @rimuroux mau tampil ke permukaan

🔥2

20 Aug 2026, 01:48 UTC85 views3 reactionsread 20 August 2026
Photo

🍀. Seseorang mencoba pergi dari pekerjaannya. Jadi mohon bantuannya, saya akan memeriksa mies sekalian demi melihat siapa yang menyembunyikannya.

3

20 Aug 2026, 01:48 UTC82 viewsread 20 August 2026
Photo

💐. Istri saya bahkan lebih prioritasin nyisirin ahoge saya daripada ketemu kalian blee, aduh maaf ya, saya ga bermaksud pamer. 😅

20 Aug 2026, 01:47 UTC86 viewsread 20 August 2026

🍀. emang boleh temen seposesif itu? emang boleh ya mies 🫣🫣

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

Citation-graph rank

Citation-graph rank — 313,975 of 1,626,711entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

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 4 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.

Names

Channels on the register whose handles appear in this channel's posts.

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

“ALYNTHUM” (@Alynthum), 6,747 subscribers as measured 27 August 2026. Telegram Register, tgregister.com/channel/Alynthum.

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.