Sticker, posted without a caption
β€3π2

Channel
@stitchgamble
On this record: Growth Β· Engagement Β· Reactions Β· Posts Β· Citations Β· Cite this entry
497subscribers
-1,840 since we began measuring on 8 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1002529399623 |
|---|---|
| Type | Channel |
| Username | @stitchgamble |
| Created | Between 1 March 2025 and 31 July 2025 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/stitchgamble |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 07:43 | 497 | -421 |
| 24 Aug 2026, 02:38 | 918 | -1,425 |
| 20 Aug 2026, 07:26 | 2,343 | +2 |
| 17 Aug 2026, 16:06 | 2,341 | +1 |
| 14 Aug 2026, 18:12 | 2,340 | +2 |
| 11 Aug 2026, 08:44 | 2,338 | +1 |
| 8 Aug 2026, 14:26 | 2,337 | no change |
| 8 Aug 2026, 01:48 | 2,337 | first reading |
20 posts held, back to 21 July 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 1 page of 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 6 August 2026. An engagement rate over an empty window would be a number about nothing.
30 reactions across 8 posts, in 4 distinct kinds. The most used accounts for 43.3% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| β€ | 13 | 43.3% | |
| π₯ | 12 | 40.0% | |
| π | 3 | 10.0% | |
| π | 2 | 6.67% |
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 8 of the 20 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 30 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 20 most recent posts we hold, published 21 July 2026 to 6 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.
Sticker, posted without a caption
β€3π2
skip
stoploss at 20K
7MkBrQ95PsZz4cL5kUmb19nMfwesbus5yr1Yefshpump Gamble 45K now
β€1
10X $WINK
π₯4
Another Robinhood play I'm keeping an eye on is $PONSLA CA: 0xc2c3645ec944ab884594d4cd3e81d026efc42983 The original dev has left the project, and it's now being led by a new community CTO team What I like is that they're staying consistent with updates on X, and the community is still active and engaged It's definitely still a high-risk gamble, but if the new team keeps building and maintains the attention, I thiβ¦
β€4
5X $WINK
π₯3
Itβs been performing well so , almost a 2x from the entry I shared with you guys. Honestly, I really like the idea behind it. The dev team seems to have a clear vision and is executing with confidence $WINK π
β€2
$WINK 0x8ad5a580c4215086dec828d8626b95a06d7d00cc This is a low-cap gem, but I actually like the setup since the dev has built in a buyback mechanism Every project launched on Cashcat Launchpad generates creator fees. 70% of those fees are automatically used to buy back & burn $WINK, while the remaining 30% is used to burn $CASHCAT DYOR
π₯5β€3
Looks like thereβs still no information at all on X. It seems the devs are planning to move fast If youβve already accepted that you could lose it all, then just hold. If youβd rather play it safe, Iβd recommend selling
btw narrative of this https://www.givesendgo.com/shilohhendrix
under 100K cutloss
Showing the 12 most recent of 20 posts we hold for @stitchgamble. 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.
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.
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 30 August 2026 β this entry's latest reading, not the date you are reading this.
βππ₯ππ₯ππ | πΎπππππβ (@stitchgamble), 497 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/stitchgamble.
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.