Channel
@openserp_cloud
On this record: Growth · Engagement · Reactions · Stars · Posts · Citations · Cite this entry
212subscribers
+4 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003672065977 |
|---|---|
| Type | Channel |
| Username | @openserp_cloud |
| Created | 22 April 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 30 August 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 1 time, most recently 30 August 2026 |
| On Telegram | t.me/openserp_cloud |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 30 Aug 2026, 06:04 | 212 | +1 |
| 23 Aug 2026, 21:15 | 211 | +1 |
| 16 Aug 2026, 06:45 | 210 | +2 |
| 8 Aug 2026, 11:05 | 208 | no change |
| 7 Aug 2026, 19:33 | 208 | first reading |
15 posts held, back to 22 April 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 pageof 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 15 posts for this entry, the most recent from 28 July 2026. An engagement rate over an empty window would be a number about nothing.
49 reactions across 13 posts, in 13 distinct kinds. The most used accounts for 20.4% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 10 | 20.4% | |
| 👍 | 9 | 18.4% | |
| 👀 | 6 | 12.2% | |
| 🆒 | 4 | 8.16% | |
| ⚡ | 3 | 6.12% | |
| ✍ | 3 | 6.12% | |
| ❤ | 3 | 6.12% | |
| 🍾 | 3 | 6.12% | |
| 😎 | 3 | 6.12% | |
| 👏 | 2 | 4.08% | |
| 👨💻 | 1 | 2.04% | |
| 🤯 | 1 | 2.04% | |
| 🫡 | 1 | 2.04% |
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 13 of the 15 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 49reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 15 most recent posts we hold, published 22 April 2026 to 28 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @openserp_cloud. Telegram publishes the count on the public post preview alongside ordinary reactions, and this register reads it there. It is the only figure on this site that measures money moving rather than attention.
Stars are not reactions, and the two are never added. They are rendered in the same strip on Telegram and counted in the same shape, but one is a tap and the other is a purchase. The reaction totals and the engagement rate elsewhere on this page exclude every figure in this section, and no rate here is computed against a reaction count.
This is not revenue, and we publish no currency figure. What a Star costs a reader and what it pays a channel are different numbers, Telegram takes a share we cannot observe, and the terms have changed. Converting a Star count into money would be an estimate dressed as a measurement, so the count is where we stop.
Counted over the 15 most recent posts we hold for this entry, published 22 April 2026 to 28 July 2026. Star counts above 1,000 reach us in Telegram’s short form and carry the same three-significant-figure rounding as everything else on this page.
New service: Search Monitor 🔍 Until now OpenSERP Cloud was one-shot - you send a query, you get a SERP. Search Monitor is the first thing that keeps running while you're not looking! Set keywords x engines x regions, pick a schedule, and it captures SERPs on its own. Hourly, daily or weekly. 🌍 Multi-engine by default Same keyword across Google, Bing, Yandex, DuckDuckGo, Baidu and Ecosia - side by side. Where engin…
👏2👀1👍1
🛠 OpenSERP v0.8.12 is out! 🥳 A lot of work done here for search stability and quality. * Browser fingerprinting - moved to native CDP overrides. Dropped the injected patch.js and localized profile files. Docker image ships updated Chrome. * Batch extraction - new POST /extract/batch, up to 20 URLs per call, returns the shape Open WebUI's web loader expects. Thanks @AIWintermuteAI * Better error reporting - captch…
🍾3❤1
🌈 OpenSERP Cloud is public! We finally launched it publicly - after alpha, fixes, engine tuning, billing work, docs, SDK examples, and a lot of SERP weirdness 😅 Big thanks to all alpha users ❤️ All alpha users will get celebration credits this week. For newcomers: - free credits are still available to start - 15% founder discount is active for a limited time - first top-up now gets +30% bonus credits Infra note: …
😎3🔥2👍1
🛠 OpenSERP Cloud update Small but useful billing + reliability changes shipped. 1. API responses now also include billing info in JSON, alongside HTTP headers: { "billing": { "credits_remaining": 1622, "credits_used": 1 } } This should make it easier to track usage without parsing headers every time. 2. Pricing is now easier to read: we described it in more detail in the dashboard and in the public pri…
👀2🆒2
🛠 OpenSERP update: release + card payments OpenSERP OSS v0.8.6 is out! 🤌 Main changes: - URL extraction is more stable now - fast extraction requests now use Chrome-like TLS, user-agent, Client Hints, and ordered headers - cleaner CLI search output for scripts and pipelines - better Google, Bing, Yandex, Baidu, and Ecosia parsing - improved SERP features, ranks, timeouts, and proxy retry handling - fixed Chrome cle…
🔥3👍1🫡1
🛠 OpenSERP notes Engine status this week: * Yandex had instability earlier in the week. The main issue should now be fixed. * Ecosia is still unstable in some cases. We are working on it. As usual: failed queries, timeouts, and empty responses are not billed. OSS updates ✅ cleaner CLI search output ✅ new extract / format flags ✅ better timeout handling ✅ improved Google, Bing, Yandex, and Ecosia result parsing ✅ b…
❤2🆒1
🛠 OpenSERP update: stability fixes + better examples Important fixes shipped for users running real workloads. Recent work focused on correctness and predictable API behavior: ✅ added support for more regions and languages in the search playground ✅ improved search result and URL extraction credit calculation ✅ fixed query limit behavior ✅ improved empty SERP handling ✅ synced API docs and playground behavior URL …
👍4👨💻1🔥1
🫂 URL extraction is now in OpenSERP! OpenSERP can now fetch a target URL and return clean markdown/text for LLM agents, RAG, and automation. Use new extract playground to prepare your query! Python SDK: from openserp import OpenSERP client = OpenSERP(base_url="http://localhost:7000") page = client.extract( url="https://openserp.org/docs", mode="auto", ) print(page.markdown) ❗️You can also enrich top se…
⚡2🔥1🤯1
🧠 Mega-search: one query, many engines Why do we need it? Which mode to use? 🔀 balanced All engines, merged + deduplicated. Billed per engine. → max coverage: RAG grounding, research, rank comparison. ⚡️ fast Engines reordered by recent health, first success wins. 1 credit. → need a good answer quickly: agent tool calls, latency-sensitive automation. 🎯 any Your exact order, first success wins. 1 credit. → you hav…
✍3👀1
🗺 Region-level search is now live New region parameter across Google, Yandex, Bing, DuckDuckGo engines. Yandex supports city-level targeting - pass a numeric region ID and get results localized to that city, not just country. Useful for: • local SEO monitoring • geo-targeted AI grounding • comparing rank differences across cities • scraping regional SERP variation Example request: GET /search?engine=yandex&query=p…
👍2🔥1🆒1
🚀 OpenSERP Cloud alpha update More users are now running real workloads through OpenSERP Cloud. Current focus: * multi-engine stability * mega-search behavior * response normalization * scaling under parallel load Alpha users currently get: * dashboard + API keys * free credits * access to all supported engines * web + image search * direct communication with the team We’re especially interested in feedback from …
👀1
Posted without readable text
Showing the 12 most recent of 15 posts we hold for @openserp_cloud. 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.
Citation-graph rank — 1,483,581 of 1,627,445entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 30 August 2026 — this entry's latest reading, not the date you are reading this.
“OpenSERP” (@openserp_cloud), 212 subscribers as measured 30 August 2026. Telegram Register, tgregister.com/channel/openserp_cloud.
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.