our lil lion is holding strong the real fun will start once we break ATH $KIO
🔥3❤1

Channel
@Philsgambleroom
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
6,082subscribers
+95 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1003354595766 |
|---|---|
| Type | Channel |
| Username | @Philsgambleroom |
| Created | Between 1 November 2025 and 31 March 2026— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/Philsgambleroom |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 21:27 | 6,082 | -12 |
| 13 Aug 2026, 14:18 | 6,094 | +48 |
| 10 Aug 2026, 10:21 | 6,046 | +59 |
| 7 Aug 2026, 05:36 | 5,987 | no change |
| 7 Aug 2026, 05:01 | 5,987 | first reading |
36 posts held, back to 4 August 2026 — the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 10 pagesof Telegram’s post history, 20 posts per page.
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.
| Window | Rolling 30 days · latest post in window 11 August 2026 |
|---|---|
| Posts held | 36 (4 August 2026 – 11 August 2026) |
| Views total | 33,826 |
| Reactions total | 334 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 04:44 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.
334 reactions across 36 posts, in 12 distinct kinds. The most used accounts for 50.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 170 | 50.9% | |
| ❤ | 116 | 34.7% | |
| 👍 | 20 | 5.99% | |
| ⚡ | 7 | 2.10% | |
| 👏 | 6 | 1.80% | |
| 💯 | 5 | 1.50% | |
| 🐳 | 2 | 0.599% | |
| 😁 | 2 | 0.599% | |
| 😱 | 2 | 0.599% | |
| 🤡 | 2 | 0.599% | |
| 🙏 | 1 | 0.299% | |
| 🤣 | 1 | 0.299% |
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 36 of the 36 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 334reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 36 most recent posts we hold, published 4 August 2026 to 11 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.
our lil lion is holding strong the real fun will start once we break ATH $KIO
🔥3❤1
fp: 0.091 almost 10x from our mention but job's not done
❤9
good buyers joining the kio gang 2m touched and more than 3x from yesterday 🦁
🔥6
2x already on $kio But we barely started Motion on our bags 🦁
🔥15❤1
gm cashcat chart playing out as expected and touching 160M again in the meanwhile cashcat NFTs to ATH, letscash ecosystem bouncing ($WINK chart looks healthy) also my recent add $KIO moving back towards 1m I think we can have a nice week ahead back to work 🫡
🔥8
i got raped on sol pairs lately so this is rather a calculated and low cortisol bet for the medium term to make it all back lol i waited a few days to see how the chart was moving and building now my bag no doubt the disney machine will do their job 🦁
🔥5❤2
ok this $KIO play is stupid asymmetric imo started sizing into it today with chart that looks bottomed after the initial candle to 3m (i was sidelined on day1) CA: 7rMnp9EJd61SvNn8LGc7SAJeQxM36oeECKmP2a7opump disney literally dropped 200m+ on a full documentary about a single lion cub going from cub to king trailer + pre-movie content already at 15m+ views combined on x and instagram the billion dollar marketing…
❤11
$WINK god candle round 2 starting soon
🔥9❤4
https://x.com/alexmccurryo/status/2086127636552794177?s=20 it's definitely not over for flamingo Alex hinting at it with the emoji new x page live with 2k+ followers already for pools.fun smelling a god candle for monday 🦩
👍5🙏1
https://x.com/PhilOnChain/status/2086033278767665474?s=20 gm, it's a game of patience
👍7
let the bird fly please
❤6🔥2
anyone needs a cash delivery bird?
👍7❤5😁2
Showing the 12 most recent of 36 posts we hold for @Philsgambleroom. 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 — 31,727 of 1,548,671entries 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.
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.
Named by 1 registered channel — 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Phil's Gamble Room” (@Philsgambleroom), 6,082 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/Philsgambleroom.
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.