Telegram RegisterThe public register of Telegram
Telegram profile photo for Liquidity Sniper

Channel

Liquidity Sniper

@Liquidity_Sniper

On this record: Growth · Engagement · Reactions · Posts · Telegram's recommendations · Cite this entry

10,684subscribers

-49 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-1001396965868
TypeChannel
Username@Liquidity_Sniper
CreatedBetween 1 April 2018 and 31 July 2021— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded7 August 2026
Last confirmed live17 August 2026
Measurements held10
Confirmed unchanged1 time, most recently 17 August 2026
On Telegramt.me/Liquidity_Sniper

Growth

10,68410,73310,708.57 August 2026 — 10,733 subscribers7 August 2026 — 10,733 subscribers8 August 2026 — 10,726 subscribers8 August 2026 — 10,725 subscribers9 August 2026 — 10,721 subscribers11 August 2026 — 10,718 subscribers12 August 2026 — 10,714 subscribers13 August 2026 — 10,707 subscribers16 August 2026 — 10,689 subscribers17 August 2026 — 10,684 subscribers7 August 202617 August 2026
10 measurements spanning 10 days, net -49. 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 10,677–10,740 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
17 Aug 2026, 12:5610,684-5
16 Aug 2026, 02:4710,689-18
13 Aug 2026, 02:1510,707-7
12 Aug 2026, 01:5210,714-4
11 Aug 2026, 00:0510,718-3
9 Aug 2026, 22:2110,721-4
8 Aug 2026, 20:5310,725-1
8 Aug 2026, 00:0110,726-7
7 Aug 2026, 12:3110,733no change
7 Aug 2026, 12:2110,733first reading

Engagement

31 posts held, back to 23 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 17 pagesof Telegram’s post history, 20 posts per page.

ERR · 30 days
12.2%
avg views ÷ 10,684 subscribers
Avg views / post
1,300
31 posts measured
Reaction rate
0.371%
reactions ÷ views · ER floor
Posts in window
31
of 31 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 22 of 31 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 12 August 2026
Posts held31 (23 July 202612 August 2026)
Views total40,332
Reactions total104
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken15 Aug 2026, 17:49 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.

Reaction mix

104 reactions across 22 posts, in 3 distinct kinds. The most used accounts for 84.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
8884.6%
👍109.62%
🔥65.77%

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

Measured over the 31 most recent posts we hold, published 23 July 2026 to 12 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

12 Aug 2026, 18:46 UTC707 views4 reactionsread 15 August 2026

Same model same line and same box Just change the date 🗓️.

4

11 Aug 2026, 13:19 UTC889 views3 reactionsread 15 August 2026

$200K for just $249? 👀 Yeah, you read that right...

3

10 Aug 2026, 18:25 UTC982 views2 reactionsread 15 August 2026

https://x.com/i/status/2086881426465759466

1🔥1

9 Aug 2026, 14:40 UTC≈1,120 views9 reactionsread 15 August 2026

https://x.com/Liq_Sniper/status/2086462633822069156?s=20

👍9

7 Aug 2026, 13:29 UTC≈1,390 views6 reactionsread 15 August 2026

https://x.com/Liq_Sniper/status/2085720010673332673?s=20

6

3 Aug 2026, 17:32 UTC≈1,680 views11 reactionsread 15 August 2026

If you've been following me for a while, you already know my model, right? 👀

6🔥5

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

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

THISSDAX KITCHEN👨‍🍳
@thedaxbrand · 95,970
Telegram ranks this channel #59 of 85 here — alongside 84 others — read 16 August 2026

This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“Liquidity Sniper” (@Liquidity_Sniper), 10,684 subscribers as measured 17 August 2026. Telegram Register, tgregister.com/channel/Liquidity_Sniper.

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.