Channel
@yummygambles
On this record: Topic · Growth · Engagement · Posts · Citations · Cite this entry
1,191subscribers
-4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001511664444 |
|---|---|
| Type | Channel |
| Username | @yummygambles |
| Created | Between 1 August 2021 and 28 February 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 7 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/yummygambles |
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 18 September 2026 and assigned it the closest of 31 fixed categories, at 54% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 05:22 | 1,191 | -10 |
| 13 Sept 2026, 03:58 | 1,201 | +14 |
| 8 Sept 2026, 21:41 | 1,187 | +1 |
| 3 Sept 2026, 06:46 | 1,186 | -3 |
| 28 Aug 2026, 12:48 | 1,189 | -1 |
| 25 Aug 2026, 02:19 | 1,190 | -4 |
| 21 Aug 2026, 23:28 | 1,194 | -1 |
| 18 Aug 2026, 20:55 | 1,195 | +5 |
| 16 Aug 2026, 03:48 | 1,190 | -1 |
| 13 Aug 2026, 00:26 | 1,191 | +2 |
| 10 Aug 2026, 05:13 | 1,189 | -5 |
| 7 Aug 2026, 14:33 | 1,194 | -1 |
| 7 Aug 2026, 06:16 | 1,195 | no change |
| 7 Aug 2026, 06:03 | 1,195 | first reading |
20 posts held, back to 15 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.
I started using @maestro since day 1 of their launch in 2022 After which many other bots were released, but i must say, my 4 years of using maestro has been unbeatable by any other bot Fast customer support, most secure in aspect of your funds, trustworthy, very good cashback, speed and lots more Maestro the best tbh Incase you not, you should 👇 https://t.me/maestro?start=r-yummymain
Aped some money cat on pools Cash cat running hard, this can be a bata 0x2d50067226ba77725a6c8ea6ca76f5414d4a55d7
Gambled some froggy Uniswap shilled it before frong https://github.com/Uniswap/interface/blob/a69a38c2fab83be09b7d4113094a49b385810c5e/packages/ui/src/assets/graphics/froggy.png https://dexscreener.com/robinhood/0x6359f8180645c303a031bcd6393cc768b4323b726dee008fd3788f4ab2b55cff
I'M ACTUALLY SHAKING Turned deposit 100$ into $2,428 on my BIGGEST WIN IN 1 SPIN Been on duelbet the last few days and ngl the odds hit different, feels like it pays out way more than anywhere else ive touched + you get a great bonus on signup Playing only here: duelbet.com
There’s an older one
Haha
🔥 Shipy [5.3x] ├ qiiiyueee └ 14.3K → 75.9K (19m) 0x43bd274a3f9f90530ea7ff2ea9c917a848b00b36
Moving btw Good wallets keeping it strong
Gambled some Shipy on eth https://dexscreener.com/ethereum/0x4315ef336b3f603372af80aa429eb669dc1aafb5
Photo, posted without a caption
Gambled a bag here Matt furie lore, 7k mc https://dexscreener.com/robinhood/0xCcbDB8593DCdb9253130D52867cA01DbCeFD1BB6
SWOGE Buy! 🤑🤑🤑🤑🤑🤑🤑🤑🤑🤑 💰 0.2013 ETH ($381.39) 🪙 494,595 SWOGE 🏷 Price: $0.0007711 🔼 Mkt Cap: $771,108 💧 Liquidity: $109,425 🔍 0xa67d...3fbb • TX 📊 Position: New! 🏹 bow.fun
Showing the 12 most recent of 20 posts we hold for @yummygambles. 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.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“YUMMY GAMBLES😋🎲” (@yummygambles), 1,191 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/yummygambles.
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.