Channel
@supadotmarket
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
230subscribers
-7 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002595172023 |
|---|---|
| Type | Channel |
| Username | @supadotmarket |
| Created | 30 July 2025 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 7 September 2026 |
| Measurements held | 6 |
| Confirmed unchanged | 1 time, most recently 7 September 2026 |
| On Telegram | t.me/supadotmarket |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Sept 2026, 01:22 | 230 | -2 |
| 30 Aug 2026, 09:03 | 232 | -2 |
| 22 Aug 2026, 08:54 | 234 | -1 |
| 15 Aug 2026, 17:08 | 235 | -2 |
| 8 Aug 2026, 10:01 | 237 | no change |
| 7 Aug 2026, 14:32 | 237 | first reading |
5 posts held, back to 30 July 2025 — 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 5 posts for this entry, the most recent from 4 January 2026. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no ≈ mark.
27 reactions across 4 posts, in 8 distinct kinds. The most used accounts for 29.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5208815510568838410 | 8 | 29.6% | |
| custom 5211145139484892438 | 5 | 18.5% | |
| custom 5210856225624824917 | 3 | 11.1% | |
| custom 5251369136004539468 | 3 | 11.1% | |
| custom 5255947571142074717 | 3 | 11.1% | |
| custom 5208816008785042972 | 2 | 7.41% | |
| custom 5251563788217361750 | 2 | 7.41% | |
| custom 5255849856341124228 | 1 | 3.70% |
Custom emoji. Every row above is a Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 4 of the 5 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 27 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 30 July 2025 to 4 January 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.
real-time return rates on supa each up/down represents the result of the round % is the return rate of the biggest win of the round and yes… all rounds are just 60-seconds ⬇️⬇️⬇️ t.me/SupaMarketBot/app t.me/SupaMarketBot/app t.me/SupaMarketBot/app
custom 52108562256248249173custom 52513691360045394683custom 52111451394848924382
some of the latest reported grabs on supa 😌 and it’s all just 1 minute trades! ⬇️⬇️⬇️ t.me/SupaMarketBot/app t.me/SupaMarketBot/app t.me/SupaMarketBot/app
custom 52111451394848924383custom 52088155105688384102custom 52515637882173617501custom 52558498563411242281
⭐️ INTRODUCING: SupaMarket ⭐️ the fastest prediction market ever built → guess if BTC goes UP or DOWN → rounds start every 60 sec → up to 15x if predicted right → real-time price data via Binance API → instant payouts → 2-lvl referral system trade now in early beta 🔥 invite frens & earn ⬇️⬇️⬇️ t.me/SupaMarketBot/app t.me/SupaMarketBot/app t.me/SupaMarketBot/app
custom 52088155105688384102custom 52088160087850429722custom 52515637882173617501custom 52559475711420747171
follow supa on X 🥹 x.com/SupaDotMarket x.com/SupaDotMarket x.com/SupaDotMarket
custom 52088155105688384104custom 52559475711420747172
Channel created
Showing the 5 most recent of 5 posts we hold for @supadotmarket. 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 7 September 2026 — this entry's latest reading, not the date you are reading this.
“supa.market TV” (@supadotmarket), 230 subscribers as measured 7 September 2026. Telegram Register, tgregister.com/channel/supadotmarket.
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.