ALL ABOARD 🚢 the @SeiNetwork! Looking to power your front-end #dApps with custom back-end #APIs? SubQuery makes it a breeze. 🌟 Create SubQuery projects to index #SEI #blockchain data in minutes! 🚀 🛠️ Learn how ➡️ https://t.co/fV0weh4pcS #web3 https://t.co/pibLX5KcG9

Channel
SubQuery Twitter
@sqsqtwitter
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
19subscribers
+0 since we began measuring on 7 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1001791522346 |
|---|---|
| Type | Channel |
| Username | @sqsqtwitter |
| Created | Between 1 December 2021 and 28 February 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 11 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/sqsqtwitter |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 11 Aug 2026, 16:46 | 19 | no change |
| 7 Aug 2026, 04:36 | 19 | first reading |
Engagement
20 posts held, back to 7 August 2023 — 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 20 posts for this entry, the most recent from 14 August 2023. An engagement rate over an empty window would be a number about nothing.
What this channel posts
- Photos
- ≈554
- Videos
- ≈350
- Links
- ≈1,050
Lifetime counters from Telegram’s own channel header, read 11 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. A count marked ≈ was rounded by Telegram before we ever saw it — t.me prints these counters in full below 1,000 and to three significant figures above, so ≈142,000 means somewhere between 141,500 and 142,499.
- Video runtime
- 1m 31s
- Average length
- 46s
Measured directly from 2 videos 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.
Recent posts
🤓 Need rock-solid data indexing? Look no further! SubQuery has your back with unbeatable reliability and uptime 🏋️♂️. Don't let maintenance slow you down - join the SubQuery squad and enjoy the #web3 indexing journey! 💪 ➡️ https://t.co/dCpfQu4tRC https://t.co/jjPBq99gQK
Hold onto your keyboards!💻 We've started supporting @BNBCHAIN & can’t wait to show you how it works. Whether you're a coding noob or programming pro🤓, we've bundled up all the info you need to learn about the $BNB tech stack & data indexing. 🧵⬇️ #binance #CZ https://t.co/oncBgk11pq
📈 When your #web3 projects demand peak performance, SubQuery delivers! 🚀 While others hit the snooze button 😴, we stay awake to ensure HIGH uptime ⏰ and constant data indexing success 💯. Say hello to SubQuery - your reliable web3 data indexer! 🚀 ➡️ https://t.co/dCpfQu4tRC https://t.co/gBjjkyuPaZ
🚀 New integration alert! 🎉 We've recently teamed up with @Eclipsefi to power amazing projects on @SeiNetwork for the @cosmos ecosystem! 🌌💥 Check out the announcement ⬇️ https://t.co/vC18KFoE0T #web3 #CosmosSDK #IBCgang $ECP
🔍 Searching for a dependable data indexer? SubQuery is here to save the day! 🦸♂️ Our uptime is as high as Mount Everest 🏔️, even when others are on maintenance mode! ⚙️ Embrace reliability and power up your #web3 projects with us! 🚀 ➡️ https://t.co/dCpfQu4tRC https://t.co/l8AvDeOsi3
SubQuery has landed on @cosmos!🚀🪐 We're moving at lightspeed, and who knows, we might even beat @elonmusk to Mars! 😅 #WatchOutSpaceX Thrilled to be supporting stellar projects like @JunoNetwork, @Fetch_ai, @StargazeZone, @SeiNetwork, @MarbleDaoCosmos, & @archwayHQ! ✨ 🧵⬇ https://t.co/ZScd45CDGB
🚨 Is your data indexing provider scheduled for a maintenance? Say hello to high uptime with SubQuery! ⏱️ We're always on duty 💪, even when others take a break ⛑️. Embrace SubQuery - your trusted indexing sidekick! 🦸♀️ ➡️ https://t.co/dCpfQu4tRC https://t.co/AuxiUDDgE7
🎉✨ Had a blast at @Paris_Dot_Comm! 🇫🇷 We geeked out over the future of #polkadot and data indexing. 🚀📊 Thanks to everyone who joined @madamczyk0 in exploring the power of SubQuery's cross-chain data indexer! 💙💪🔍 Read more ⬇️ https://t.co/SLcE1F5dcM #web3 #dataindexing
The latest Kepler Network stats are looking stellar! ✨ Keep up the excellent work, Indexers and Delegators! 💪 #web3 #dataindexing https://t.co/9DSnc8EEGZ
📢 Calling all Indexers, our weekly Kepler Office Hours is happening in 30min! ⏰ Find out the latest on the state of our Kepler Network & indexing 👀 Everyone is welcome! 😉 Join us on Discord⬇ https://t.co/s9l5X8VGLG #web3 #dataindexing https://t.co/9pDzsBgN60
Hey devs👋🤓 We've got awesome news for you: 1️⃣ New indexing support on @SeiNetwork, @gnosischain & @archwayHQ 2️⃣ Improvements to @Algorand 3️⃣ Significantly reduced gas costs and more! ⛽ Check out our developer monthly update⬇ https://t.co/nZzQaNA2C7 #web3
Showing the 12 most recent of 20 posts we hold for @sqsqtwitter. 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.
Mentions
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.
Handles this channel named that no longer answer
- Dead references
- 5
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 5
- vacant every time we have ever looked
@sqsqtwitter named 5 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
named in 1 post, 12 August 2026 – 12 August 2026
Cite this entry
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 11 August 2026 — this entry's latest reading, not the date you are reading this.
“SubQuery Twitter” (@sqsqtwitter), 19 subscribers as measured 11 August 2026. Telegram Register, tgregister.com/channel/sqsqtwitter.
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.