Channel
@salamoonder_telegram
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
696subscribers
+25 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001870070759 |
|---|---|
| Type | Channel |
| Username | @salamoonder_telegram |
| Created | Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 6 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 6 October 2026 |
| On Telegram | t.me/salamoonder_telegram |
Technology — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 81% 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 |
|---|---|---|
| 6 Oct 2026, 06:57 | 696 | +2 |
| 25 Sept 2026, 21:21 | 694 | +7 |
| 10 Sept 2026, 10:39 | 687 | +2 |
| 31 Aug 2026, 08:23 | 685 | +1 |
| 24 Aug 2026, 22:13 | 684 | +7 |
| 16 Aug 2026, 18:07 | 677 | +3 |
| 8 Aug 2026, 23:02 | 674 | +3 |
| 8 Aug 2026, 02:33 | 671 | no change |
| 7 Aug 2026, 23:22 | 671 | first reading |
20 posts held, back to 10 March 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 24 July 2026. An engagement rate over an empty window would be a number about nothing.
82 reactions across 17 posts, in 5 distinct kinds. The most used accounts for 41.5% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ❤ | 34 | 41.5% | |
| 🔥 | 22 | 26.8% | |
| 👍 | 19 | 23.2% | |
| 👌 | 5 | 6.10% | |
| 🥰 | 2 | 2.44% |
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 17 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 82 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 10 March 2026 to 24 July 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.
Hi everyone, Noticed degraded performance on Kasada protected sites? Here's why: several sites have tightened their header requirements and other checks. If that's affecting you, reach out, we're real people here, not bots, and we'd rather you ask five times than struggle in silence once. We can build you a custom demo or help adjust your code. Just tell us which site, what error you're seeing, and share your code,…
❤8👍1
Hey everyone, We experienced some downtime overnight. Since it happened while our team was asleep, there was a short delay before we could get a fix out, sorry for the inconvenience. Everything is back up and running normally now. We've also made some changes on our end to help prevent this kind of issue from happening again going forward. Kind Regards, The Salamoonder Team
Hey everyone, thanks for your patience. I pushed an update to our standard task around 10:40 (GMT+3). Quick note for anyone relying on Salamoonder: please add a backup to your production code that falls back to our payload task, since that's been working reliably throughout the day. Some sites might have issues with the standard task, if you notice anything, just let us know.
👍4
Hey everyone, we're currently updating our Standard task. If you haven't already you can switch to our payload task. https://apidocs.salamoonder.com/tasks/kasada/payload We will send an announcement once we've pushed an update.
👍5
Resolved, sorry for any inconvenience caused. 🤝
We are aware the API is not reachable, we're working on it now.
👌1
Solved, if you asked us a question but received no response send it again 🤝
❤4
Our support bot is having some issues, we will send a message here once it’s resolved and then send your questions again if you haven’t received an answer.
❤2
Hey everyone, I hope you're all doing well! 😊 We've just shipped an update to our DataDome task, and it's a big improvement to the flow! What's changed: Instead of returning the cookie directly, we now return the solved challenge URL. From there, all you need to do is make a simple GET request to retrieve your cookie. Clean and straightforward! If you're using our SDK: Please make sure to update to the newest vers…
❤6🥰2
Hey everyone, It's been a while since we've posted an update. When everything is running smoothly, we don't see much value in sending messages just for the sake of it. That said, our silence definitely doesn't mean we've been inactive. We've been working on a major project behind the scenes. We can't share too many details just yet, but we can say it's well worth the wait. The project is mainly focused on Twitch, K…
🔥6
Hey, our support team is off today due to King’s Day 🇳🇱. If you don’t hear back today, we’ll get to it first thing tomorrow morning.
❤1
If your ticket was missed or you felt like it didn’t get the attention it should have, please feel free to bump it. It’s been a busy period on our side, and there’s a chance your message slipped through. We’ll make sure to take a look as soon as we see it. 😊
Showing the 12 most recent of 20 posts we hold for @salamoonder_telegram. 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 6 October 2026 — this entry's latest reading, not the date you are reading this.
“Salamoonder (BETA) Telegram” (@salamoonder_telegram), 696 subscribers as measured 6 October 2026. Telegram Register, tgregister.com/channel/salamoonder_telegram.
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.