Telegram RegisterThe public register of Telegram
Telegram profile photo for Liam's gems calls

Channel

Liam's gems calls

@LiamsGemCalls

On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry

19,954subscribers

-3,622 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-1002122935346
TypeChannel
Username@LiamsGemCalls
CreatedBetween 1 November 2023 and 31 May 2024 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live19 September 2026
Measurements held33
Confirmed unchanged1 time, most recently 19 September 2026
On Telegramt.me/LiamsGemCalls

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 98% 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 why it has no browse page of its own yet.

Growth

19,43624,27321,854.57 August 2026 — 23,576 subscribers7 August 2026 — 23,572 subscribers8 August 2026 — 23,285 subscribers9 August 2026 — 23,160 subscribers10 August 2026 — 23,101 subscribers11 August 2026 — 22,765 subscribers12 August 2026 — 22,678 subscribers13 August 2026 — 22,490 subscribers14 August 2026 — 22,146 subscribers16 August 2026 — 21,967 subscribers17 August 2026 — 24,273 subscribers18 August 2026 — 23,932 subscribers19 August 2026 — 23,528 subscribers20 August 2026 — 23,125 subscribers21 August 2026 — 22,703 subscribers23 August 2026 — 22,196 subscribers24 August 2026 — 21,612 subscribers26 August 2026 — 21,320 subscribers26 August 2026 — 21,037 subscribers28 August 2026 — 20,613 subscribers29 August 2026 — 20,258 subscribers30 August 2026 — 19,958 subscribers31 August 2026 — 19,716 subscribers1 September 2026 — 19,436 subscribers2 September 2026 — 24,194 subscribers3 September 2026 — 23,806 subscribers5 September 2026 — 23,218 subscribers8 September 2026 — 22,406 subscribers11 September 2026 — 21,542 subscribers13 September 2026 — 20,829 subscribers14 September 2026 — 20,512 subscribers16 September 2026 — 20,307 subscribers19 September 2026 — 19,954 subscribers19,9547 August 202619 September 2026
33 measurements spanning 43 days, net -3,622. 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 18,710–24,999 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 33
Measured (UTC)SubscribersChange
19 Sept 2026, 08:0119,954-353
16 Sept 2026, 20:1820,307-205
14 Sept 2026, 23:5920,512-317
13 Sept 2026, 12:1720,829-713
11 Sept 2026, 13:1821,542-864
8 Sept 2026, 20:0022,406-812
5 Sept 2026, 13:3523,218-588
3 Sept 2026, 16:1923,806-388
2 Sept 2026, 07:5624,194+4,758
1 Sept 2026, 07:2719,436-280
31 Aug 2026, 06:1419,716-242
30 Aug 2026, 03:2919,958-300
29 Aug 2026, 00:4320,258-355
28 Aug 2026, 00:2420,613-424
26 Aug 2026, 22:2621,037-283
26 Aug 2026, 00:4221,320-292
24 Aug 2026, 22:3521,612-584
23 Aug 2026, 08:0422,196-507
21 Aug 2026, 21:2822,703-422
20 Aug 2026, 15:3423,125first reading

Engagement

123 posts held, back to 27 July 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 62 pages of Telegram’s post history, 20 posts per page.

ERR · 30 days
8.10%
avg views ÷ 19,954 subscribers
Avg views / post
1,620
28 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
28
of 123 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 1 September 2026
Posts held123 (27 July 20261 September 2026)
Views total45,250
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken3 Sept 2026, 13:09 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

1 Sept 2026, 19:01 UTC≈1,450 viewsread 3 September 2026

0x4062083510f67d28844Df9371244E6F191B97777 https://x.com/naiivememe/status/1891115853904539954 https://www.binance.com/en/square/post/24644493464970

31 Aug 2026, 21:38 UTC≈1,550 viewsread 3 September 2026
Photo

(🔥HYPE) Perp $PERP Pepe just launched on Hyperliquid from PerpMe, the new $HYPE launchpad. PerpMe is a fresh HyperEVM launchpad, similar to $STONK and $PONS. You can trade Perps with $PERP on https://perp.world, with Long, short, and leveraged positions all decentralized on HYPE chain. Just launched and moving well already. Team has done well in the past. $PERP is building a community of real leverage traders, perfo

31 Aug 2026, 18:09 UTC≈1,780 viewsread 3 September 2026
Photo

dcaing $ram https://dexscreener.com/robinhood/0x5860dd468b4fc1740eaf80a3b7f22e78d70a076a ___ APE3

30 Aug 2026, 19:43 UTC≈1,580 viewsread 3 September 2026

#brotherhood https://dexscreener.com/robinhood/0x1318b3ffba2a8f04a9ce03b2370705c4e17040c5303436ab84e7831912c6c1c3

30 Aug 2026, 12:27 UTC≈1,560 viewsread 3 September 2026
Photo

SOL $OSCAR just launched watch entries! Oscar is the king of ai cats and world powerslap champion/ambassador https://x.com/i/communities/2037661091090567578 https://www.instagram.com/reel/DcjlL2cJL0B/ Crc9kuYPWG5pJwrNS8MeUq72Bbxxnw9nh42LkSoMpump https://dexscreener.com/solana/dwwck3yfcx17yyow6mrbyhfldci4d1z8ckhiy5onf57k Promo

30 Aug 2026, 01:04 UTC≈1,560 viewsread 3 September 2026

$PIZZA - 140K - Dyor - NFA 0x8554D38b95E4F7Ca11D391008627Df30B2b07777

29 Aug 2026, 19:59 UTC≈1,460 viewsread 3 September 2026
Photo

$SPACETIME - Robinhood was actually called Spacetime LLC before it became Cashcat then Robinhood, dev even dug up the old logo and article, wild lore ngl. 0x18878347b7B5b1Ca325a4b6a3b5Bc921b4DE7d3C https://dexscreener.com/robinhood/0x0881a9eece2a49c3d7a3abb95bb9c605a6b2d6a1 https://x.com/bagwalkbw/status/2079968281289740569 https://archive.ph/20240603082441/ https://www.wsj.com/articles/DJFVW00020131218e9cidr0c8

29 Aug 2026, 19:52 UTC≈1,670 viewsread 3 September 2026

AUTSM Waiting for entry paired with tsm https://www.geckoterminal.com/robinhood/pools/0xa656346c328c7185f783e78936b68eb5868aa9cf5809260320b279f7e13790fc 0xd4aae326ddd1a2537a92c00e6576e4605e5d1e18 Promo

29 Aug 2026, 18:41 UTC≈1,350 viewsread 3 September 2026

Taiyi Watching this https://x.com/taiyibsc?s=21 https://www.geckoterminal.com/bsc/pools/0x7d87084ce606f103325c866be20f8fcdd3527982 0x11116f6fc6145fe83e1e11f363210f90e2761111

29 Aug 2026, 14:41 UTC≈1,710 viewsread 3 September 2026
Photo

SOL $monke just launched! $MONKE no thoughts. head empty. hands buying. He was drawn in four minutes by someone who has never seen an orangutan in person. He has no utility, no VC, no Telegram admin named Kevin. What he has is a face — and pump.fun does not have one yet. That's the whole plan. https://www.monkeonsolana.com/ https://x.com/retardmonke FXs5242SBs4J1Bt6Q6usuxB8Ju1SNApQBPbPSVXupump Promo

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

Posts edited after publishing

@LiamsGemCalls 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
22 August 2026
Most recent edit
22 August 2026

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

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

“Liam's gems calls” (@LiamsGemCalls), 19,954 subscribers as measured 19 September 2026. Telegram Register, tgregister.com/channel/LiamsGemCalls.

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.