Channel
@xltable_news
On this record: Growth · Engagement · Reactions · Posts · Citations · Cite this entry
23subscribers
+6 since we began measuring on 8 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003321099530 |
|---|---|
| Type | Channel |
| Username | @xltable_news |
| Created | Between 1 November 2025 and 5 January 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 11 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/xltable_news |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 17 Sept 2026, 18:19 | 23 | +5 |
| 31 Aug 2026, 06:33 | 18 | +1 |
| 11 Aug 2026, 20:46 | 17 | no change |
| 8 Aug 2026, 00:18 | 17 | first reading |
20 posts held, back to 5 January 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 20 July 2026. An engagement rate over an empty window would be a number about nothing.
225 reactions across 20 posts, in 6 distinct kinds. The most used accounts for 38.2% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 86 | 38.2% | |
| 👍 | 64 | 28.4% | |
| ❤ | 43 | 19.1% | |
| 👏 | 23 | 10.2% | |
| 🤩 | 8 | 3.56% | |
| 🤯 | 1 | 0.444% |
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 20 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 225 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 5 January 2026 to 20 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.
XLTable 2.0.16 + 2.0.17 — built for production 🚀 Two releases focused on running XLTable at enterprise scale — clusters, caching, and everything your DBA will ask about. ▪️ Multi-server deployments — several XLTable servers now share one cache through Redis and run behind a load balancer, no sticky sessions. Sessions, query cancellation, license counting and cache management all work cluster-wide. ▪️ Shared SQL cache…
🔥3🤩3👍2
Unpopular opinion in data engineering: Excel is not the enemy. The enemy is the zoo of tools we deploy trying to pull people out of it — and the exports, copies and "several versions of the truth" that follow when people go back to Excel anyway. They always do. So we built XLTable on the opposite bet: make Excel a first-class, governed interface to big data. One XMLA semantic layer over ClickHouse, BigQuery, Snowf…
🔥4👏2👍1
The same metric: 27 lines of YAML — or 5 lines of SQL. 🚀 New post on why XLTable defines its semantic layer in plain SQL instead of YAML. The core principle: every block of a cube definition is an executable SELECT — copy it into any database client and it runs. So debugging is execution, reviews are code reviews, and AI writes these definitions fluently — then queries the same governed cube via MCP. Including an …
👍4🔥3🤯1
XLTable 2.0.15 + 2.0.14 🚀 ▪️ Drillthrough is here — the most requested feature. Double-click any Pivot Table cell to see the underlying detail rows. Detail columns are configurable per measure group. ▪️ Collapse / Expand Entire Field — full support for all combinations, including multi-level hierarchies. Collapsed fields aren't even queried — their tables are skipped entirely until expanded. ▪️ Keep Only / Hide Se…
🤩5🔥4👍3
🚀 New article: why Excel is still the #1 self-service analytics tool — and why that's actually fine. Covered: — The real bottleneck (it's the data, not the spreadsheet) — Where AI chat fits vs where Excel fits — How an OLAP semantic layer changes the equation 📖 https://xltable.com/blog/excel-self-service-analytics
🔥5👍3❤1
🚀 XLTable now supports MCP (Model Context Protocol) XLTable now supports MCP, allowing AI assistants and LLM applications to access data and metadata through a standardized protocol. ✅ Access semantic models, dimensions, and measures defined in XLTable ✅ Use trusted business definitions in AI applications ✅ Connect AI tools through a governed semantic layer ✅ Integrate with modern MCP-compatible ecosystems With MC…
👍5❤4🔥3
🚀 XLTable 2.0.12 Released We're excited to announce XLTable version 2.0.12 with new connectivity and performance improvements. ✅ Greenplum Connector XLTable now supports Greenplum as a data source, expanding the range of analytical platforms available through Excel. ✅ HTTP gzip Compression Server responses now support gzip compression, reducing network traffic and improving data transfer efficiency. ✅ Faster XMLA…
❤5🔥4👍2
🚀 XLTable at a joint webinar with AXENIX On May 21 at 16:00 UTC+3, AXENIX will host a webinar dedicated to XLTable — an OLAP system for working with data in ClickHouse and Trino, with XMLA support and direct connectivity from Excel Pivot Tables. During the webinar, we will show how XLTable helps companies: 🔸 connect Excel directly to modern analytical databases 🔸 work with large datasets without exports or data dup…
🔥5👍4❤3
🚀 XLTable in action We were excited to see a great example of XLTable used as the foundation for a practical Excel analytics workflow. The idea is simple: take data from a modern data warehouse and make it available in Excel as a cube. Data Warehouse → XLTable → Excel It is great to see how XLTable can power simple, accessible, and familiar analytics experiences for users. Many thanks to the author for sharing t…
❤6🔥4👍3
🚀 Version 2.0.11 is live Three updates worth knowing about: ✅ Databricks Connector — Databricks is now supported as a data source. Connect your pipelines directly without extra workarounds. ✅ OLAP cube syntax validation — validate your cube definition syntax before loading. Catch errors early, save time on debugging. ✅ Windows 10 & 11 support — the app now runs natively on Windows 10 and 11. Update now 👇 https:…
🔥6👍3👏1
🚀 One of our clients has shared a public review about XLTable on LinkedIn. It is always especially valuable to see feedback from real users who apply XLTable in practice to connect Excel with modern data platforms and work with large datasets in a familiar interface. We truly appreciate this trust and kind words. Thank you for supporting XLTable and sharing your experience with others. 🙏❤️ Such feedback inspires u…
👍5🔥5👏2
🚀 XLTable + Snowflake: From Zero to Pivot Table in 15 Minutes We just published a step-by-step quickstart guide — connect Excel directly to Snowflake via XLTable and get a live Pivot Table with no CSV exports, no BI tools, no plugins. What's inside: — A ready-to-run SQL script that creates a realistic data model (sales, inventory, regions, managers) — XLTable setup in minutes — the OLAP cube is defined straight in t…
🔥4❤3👍3👏3
Showing the 12 most recent of 20 posts we hold for @xltable_news. 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.
Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.
Named by
Channels on the register whose posts name this channel's handle.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“XLTable News 📢” (@xltable_news), 23 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/xltable_news.
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.