140mil 1 week x2.5+) low risk any size
β€2π2π1πΏ1

Channel
@cryptoubah
On this record: Topic Β· Growth Β· Engagement Β· Reactions Β· Posts Β· Cite this entry
31subscribers
-1 since we began measuring on 7 August 2026
Risers and fallers across the register Β· movement among entries of Under 1,000.
| Telegram ID | -1002107904318 |
|---|---|
| Type | Channel |
| Username | @cryptoubah |
| Created | Between 1 November 2023 and 31 May 2024 β estimated from Telegramβs id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 8 October 2026 |
| Measurements held | 3 |
| Confirmed unchanged | 2 times, most recently 8 October 2026 |
| On Telegram | t.me/cryptoubah |
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 30 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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 |
|---|---|---|
| 27 Sept 2026, 05:35 | 31 | -1 |
| 11 Aug 2026, 02:31 | 32 | no change |
| 7 Aug 2026, 16:09 | 32 | first reading |
19 posts held, back to 13 November 2024 β 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 19 posts for this entry, the most recent from 2 January 2025. An engagement rate over an empty window would be a number about nothing.
21 reactions across 8 posts, in 6 distinct kinds. The most used accounts for 42.9% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| π | 9 | 42.9% | |
| β€ | 8 | 38.1% | |
| π | 1 | 4.76% | |
| π | 1 | 4.76% | |
| πΏ | 1 | 4.76% | |
| π | 1 | 4.76% |
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 19 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 21 reactions in total: the kind of figure the paragraph above means by βa reaction total printed elsewhere on the pageβ.
Measured over the 19 most recent posts we hold, published 13 November 2024 to 2 January 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
140mil 1 week x2.5+) low risk any size
β€2π2π1πΏ1
$send https://photon-sol.tinyastro.io/en/lp/6s9EJAwWNEAK4QuxFVy75L34YxWCEM62PxLTuipuVCoW?handle=1076869ea2193b0a2223ac Low risk bid at this price, half of size now and half if 53mil$ 1-2 week hold aiming at x2+ https://x.com/sendaifun/status/1871538621674918311 softshill by toly and solana, imo can't be lower than 53mil so its good bid
β€3π2π1
around 4x π
β€1π1
$WILLY ansem frank in animals meta coming back 6KVcC37iUeYmAS1kMUFEi3kS9G91tA8isqZ54ebgpump 1kk$
β€1π1
33kk, 6x ez
β€1π1
7D1iYWfhw2cr9yBZBFE6nZaaSUvXHqG5FizFFEZwpump $YNE cabal shit looks like runner to 10-20kk, look for entry, 4.5kk now
π1
35kk mcap 3.5x ATH, gz who hold π
π1
2.5x
find entry in strong AI project with support of big players in space, good sentiment in X $grift was afk yesterday so topblast today for couple xs, entered at 10.5kk$, https://photon-sol.tinyastro.io/en/lp/7dXUXn2dxTydHi2yWqvvqJwEWoB9mLFTh4hzDDowKVJY?handle=794449a1a643aa77cb865
lol )
adding $giga 325kk$ with dca on 305$kk and 270kk$ (low chance) ATH on 750kk$ strong community and viral meme chart is very good looking big volume on dips https://photon-sol.tinyastro.io/en/lp/4xxM4cdb6MEsCxM52xvYqkNbzvdeWWsPDZrBcTqVGUar?handle=794449a1a643aa77cb865
$mona 1.45kk$ mcap MoNAoCoXKLb38Y2VpbukGacdNYhvRTyVn92DvRApXep easy 2-3x retrace when they'll post update.
Showing the 12 most recent of 19 posts we hold for @cryptoubah. 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.
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 27 September 2026 β this entry's latest reading, not the date you are reading this.
βgoldmine beer πβ (@cryptoubah), 31 subscribers as measured 27 September 2026. Telegram Register, tgregister.com/channel/cryptoubah.
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.