Telegram RegisterThe public register of Telegram

Channel

ន៣ ᳵ 𝙷𝚊𝚌𝚔𝚜

@SMLua

On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry

442subscribers

-3 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1001363452809
TypeChannel
Username@SMLua
Created10 January 2020measured — cross-checked against a third-party dataset (TGDataset)
First recorded6 August 2026
Last confirmed live12 August 2026
Measurements held3
Confirmed unchanged1 time, most recently 12 August 2026
On Telegramt.me/SMLua

Growth

442445443.56 August 2026 — 445 subscribers6 August 2026 — 445 subscribers12 August 2026 — 442 subscribers6 August 202612 August 2026
3 measurements spanning 6 days, net -3. 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 442–445 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
12 Aug 2026, 20:03442-3
6 Aug 2026, 19:17445no change
6 Aug 2026, 17:54445first reading

Engagement

20 posts held, back to 2 January 2022the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 pageof 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 14 April 2023. An engagement rate over an empty window would be a number about nothing.

Recent posts

14 Apr 2023, 11:51 UTC≈2,000 viewsread 6 August 2026

Remember when i said that @|NHNHNH000 is scammer, he is back and we want you all to get him banned again, he faked into getting his second username: @FHFHFH333 and now want to get more scams ! 🚫 Report Scammer 🚫 @|Ninosaur_5 🚫 SCAM 🚫

Signed 三弐勻。!

8 Jan 2023, 12:00 UTCviews —

ន៣ ᳵ 𝙷𝚊𝚌𝚔𝚜 pinned «-- @NHNHNH000 -- ⚠️ This user has been highly known as scammer , we're alerting everyone to keep the environment safe for everyone.»

8 Jan 2023, 12:00 UTC≈1,620 viewsread 6 August 2026

-- @NHNHNH000 -- ⚠️ This user has been highly known as scammer , we're alerting everyone to keep the environment safe for everyone.

Signed 三弐勻。!

3 Jun 2022, 23:50 UTC≈2,660 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,600 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,540 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,450 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,360 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,280 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,190 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,130 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

3 Jun 2022, 23:50 UTC≈2,070 viewsread 6 August 2026

>>> @SMXCheats <<<

Signed 中〆 𓆩ĐⱥɍҟꞨħⱥđēꞩ𓆪

Showing the 12 most recent of 20 posts we hold for @SMLua. 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 — 374,174 of 1,189,255entries 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

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.

Mentions

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

“ន៣ ᳵ 𝙷𝚊𝚌𝚔𝚜” (@SMLua), 442 subscribers as measured 12 August 2026. Telegram Register, tgregister.com/channel/SMLua.

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.