🎉 You asked — we listened. We’ve received a lot of feedback that the 12-hour trial wasn’t enough. So starting now, every new user gets a full 24-hour free trial with all features unlocked. More time to test it properly, run a full shift, and see how LumosWS works for you. Tell your friends 🚀

Channel
Lumos Bot App
@getlumos
On this record: Topic · Growth · Engagement · Reactions · Posts · Cite this entry
786subscribers
-88 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 | -1004395852437 |
|---|---|
| Type | Channel |
| Username | @getlumos |
| Created | 13 July 2026 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 15 |
| Confirmed unchanged | 1 time, most recently 16 November 2026 |
| On Telegram | t.me/getlumos |
Topic
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 19 September 2026 and assigned it the closest of 31 fixed categories, at 70% 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 the other topics.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 15:44 | 786 | -11 |
| 6 Nov 2026, 16:26 | 797 | -15 |
| 29 Oct 2026, 20:28 | 812 | -16 |
| 22 Oct 2026, 13:08 | 828 | -10 |
| 14 Oct 2026, 13:37 | 838 | -7 |
| 7 Oct 2026, 02:00 | 845 | -9 |
| 25 Sept 2026, 14:58 | 854 | -5 |
| 13 Sept 2026, 07:36 | 859 | -4 |
| 4 Sept 2026, 20:38 | 863 | -3 |
| 27 Aug 2026, 15:24 | 866 | -5 |
| 21 Aug 2026, 05:53 | 871 | -5 |
| 14 Aug 2026, 21:14 | 876 | +3 |
| 8 Aug 2026, 01:16 | 873 | no change |
| 7 Aug 2026, 23:33 | 873 | -1 |
| 7 Aug 2026, 19:39 | 874 | first reading |
Engagement
14 posts held, back to 13 July 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 14 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Reaction mix
3 reactions across 2 posts, in 2 distinct kinds. The most used accounts for 66.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🔥 | 2 | 66.7% | |
| ❤ | 1 | 33.3% |
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 2 of the 14 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 3 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 14 most recent posts we hold, published 13 July 2026 to 3 August 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.
Recent posts
⚠️ Service Update Earlier today, some users experienced connection issues. Our hosting provider was performing technical maintenance, which affected part of our infrastructure. We’ve already migrated everything to new servers, making the system much more resilient to situations like this going forward. 🚀 If you’re still experiencing any issues, just message our support team we’ll get everything sorted out as quick…
👋 Hey! You’ve probably noticed that Spark has been rolling out app updates. One of the latest changes adds tips directly to the main offer card. The update hasn’t reached everyone yet, but we’ve already released a patch that correctly recognizes and parses the new card layout. Just update to the latest version, and you’re good to go 🚀
Lumos bot app pinned «🫠We’ve already seen people trying to clone Lumos... so funny, but remember: fake is still a fake. You have no idea what’s been changed under the hood, and it’s not worth risking your Spark account. The only official places to get Lumos for Walmart Spark are:…»
🫠We’ve already seen people trying to clone Lumos... so funny, but remember: fake is still a fake. You have no idea what’s been changed under the hood, and it’s not worth risking your Spark account. The only official places to get Lumos for Walmart Spark are: 🤖 Telegram: @lumos_ws_bot 🌐 Website: getlumos.app
🚨 BIG LUMOS UPDATE Yo! This is probably the biggest update we’ve shipped so far. We completely tore Spark apart, learned a ton about how it behaves, and rebuilt the Lumos core from the ground up. The result? At least 80% faster while staying just as stable and reliable. Here’s what’s new: 🧠 Smart Mode 2.0 – Now puts more weight on your payout filter while still staying flexible enough to catch great offers that b…
👋 Hey everyone! Have you ever noticed that Spark sometimes feels… slow? Offers take forever to load, the app freezes for a second, random reloads happen, and by the time everything catches up, the offer is already gone. Most people blame their internet connection or their phone. We did a deep dive into the Spark app, and we found something interesting. It looks like the app intentionally throttles parts of its own…
❤1
👋 Yo, everyone! The new update is finally ready. We’ve spent the last few days testing it on real shifts, and everything’s looking solid. Here’s what’s new: ✅ Drop-off filter – You can now set the maximum number of drop-offs you’re willing to take, making it easier to avoid those long multi-stop orders. ✅ Skip Pharmacy orders – Don’t like pharmacy deliveries? Now you can automatically skip them. ✅ Cleaner Histor…
🔥2
Today’s all about testing the new build Tomorrow we’re pushing a new update with a couple of new features and improved response times on high-end Android phones (like pixel 9-10)
Lumos bot app pinned «👋 Yo, guys! Welcome to the official Lumos channel! This is where I'll be sharing development updates, new features, behind-the-scenes progress, and everything important about the project. From day one, we had one goal: build the best product on the market.…»
👋 Yo, guys! Welcome to the official Lumos channel! This is where I'll be sharing development updates, new features, behind-the-scenes progress, and everything important about the project. From day one, we had one goal: build the best product on the market. But our priority has never been just clicking faster. Our #1 priority is keeping your account safe. Speed comes second. That's why we've spent months building …
Channel photo updated
Showing the 12 most recent of 14 posts we hold for @getlumos. 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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“Lumos Bot App” (@getlumos), 786 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/getlumos.
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.