Channel
@splox_ai
On this record: Growth · Engagement · What this channel posts · Reactions · Stars · Posts · Citations · Cite this entry
233subscribers
+0 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002353812654 |
|---|---|
| Type | Channel |
| Username | @splox_ai |
| Description | Main: https://splox.io Splox App: https://app.splox.io/ |
| Created | 28 October 2024 — measured — dated from the channel’s first post |
| First recorded | 7 August 2026 |
| Last confirmed live | 7 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/splox_ai |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 7 Aug 2026, 02:47 | 233 | no change |
| 6 Aug 2026, 08:36 | 233 | first reading |
7 posts held, back to 28 October 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 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 7 posts for this entry, the most recent from 5 December 2025. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 7 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
120 reactions across 6 posts, in 5 distinct kinds. The most used accounts for 35.8% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5323547156630483403 | 43 | 35.8% | |
| custom 5353025608832004653 | 39 | 32.5% | |
| custom 5217824874487101321 | 24 | 20.0% | |
| custom 5197630131534836123 | 10 | 8.33% | |
| custom 5352640560718949874 | 4 | 3.33% |
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 areTelegram’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 6 of the 7 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 120reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 7 most recent posts we hold, published 28 October 2024 to 5 December 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.
A paid reaction is a reader spending Telegram Stars — bought with money — on a post by @splox_ai. 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 7 most recent posts we hold for this entry, published 28 October 2024 to 5 December 2025. 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.
Local Machine Connector — now available Splox agents can now run tasks directly on your machine — download models, execute code, access files, fix configs. Like having an engineer available 24/7, except instant. No uploads. No manual setup. Just describe what you need. Download Splox App
custom 535302560883200465311custom 52178248744871013214custom 53235471566304834034
Here’s another beginner-friendly use case you can build with the previous tutorial: automated data analysis. Using the workflow, you can upload any file and have the agent read it, clean it, analyze patterns, and generate insights completely on its own. It can send the results straight to Telegram, WhatsApp, or to your workspace tools like Slack, write a polished report into Notion, or update dashboards in Google Sh…
custom 53235471566304834036custom 51976301315348361233custom 53530256088320046531
Deploy Ghost CMS to splox-sandbox.app One prompt. The agent bought a server, configured nginx, SSL, database, and deployed the app. Full DevOps experience. Full Chat Session
custom 52178248744871013216custom 53235471566304834031custom 53530256088320046531
Connect AI to Your Data Sources This tutorial teaches how to connect multiple platforms to a single AI agent. You'll set up Google Sheets, Notion, and Slack integrations—then run workflows that read, process, and write data across all of them. The example builds a customer feedback analyzer, but the same pattern works for any multi-platform workflow. Dataset included so you can follow along immediately. Tutorial …
custom 53235471566304834039custom 52178248744871013211custom 53530256088320046531
Splox is now publicly available. Splox is a platform for building autonomous AI agents that execute real tasks. Agents can run code, access 5000+ tools including web scraping and databases, and scale from 1 to 1000 parallel instances easily. We've launched with comprehensive documentation and tutorials. Our first tutorial walks through building a simple agent—all in under 2 minutes with no coding required. More tu…
custom 532354715663048340313custom 51976301315348361237custom 53530256088320046534
Splox is live on Product Hunt! After 1.5 years of building, I’m finally launching Splox publicly today. Splox is a multi-agent platform where AI agents can collaborate, schedule each other, and even build tools for themselves. If you’ve been following the journey — this is the moment 🎉 Product Hunt Link Your support means a lot!
custom 535302560883200465321custom 521782487448710132113custom 532354715663048340310custom 53526405607189498744
Channel created
Showing the 7 most recent of 7 posts we hold for @splox_ai. 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.
Stars beside a post are paid reactions — Telegram Stars, bought with money and spent on that post. They are a different unit from reactions and are never added to them, here or anywhere else on this page.
Citation-graph rank — 114,481 of 1,160,990entries 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.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“SPLOX” (@splox_ai), 233 subscribers as measured 7 August 2026. Telegram Register, tgregister.com/channel/splox_ai.
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.