#EF7_ESP_SP (spoofer temporarily removed) Added a separate color for bosses and their followers. Added Battle Pass items.
![Telegram profile photo for Soft[HUB]](https://cdn.tgregister.com/av/73/73e7aef82de0289f5726fad8706a935accfbd8763a4a9132027624c1882bd61d.jpg)
Channel
Soft[HUB]
@softhubdev
On this record: Topic · Growth · Engagement · Posts · Cite this entry
612subscribers
+40 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 | -1001250237119 |
|---|---|
| Type | Channel |
| Username | @softhubdev |
| Created | Between 1 March 2018 and 31 August 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 12 October 2026 |
| Measurements held | 9 |
| Confirmed unchanged | 1 time, most recently 12 October 2026 |
| On Telegram | t.me/softhubdev |
Topic
Gaming — 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 20 September 2026 and assigned it the closest of 31 fixed categories, at 93% 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 why it has no browse page of its own yet.
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 12 Oct 2026, 21:16 | 612 | -3 |
| 18 Sept 2026, 04:59 | 615 | +9 |
| 10 Sept 2026, 18:21 | 606 | +8 |
| 1 Sept 2026, 13:25 | 598 | +10 |
| 24 Aug 2026, 14:08 | 588 | +8 |
| 16 Aug 2026, 14:56 | 580 | +7 |
| 8 Aug 2026, 08:26 | 573 | +1 |
| 8 Aug 2026, 03:31 | 572 | no change |
| 7 Aug 2026, 18:53 | 572 | first reading |
Engagement
20 posts held, back to 29 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 20 posts for this entry, the most recent from 7 August 2026. An engagement rate over an empty window would be a number about nothing.
Recent posts
#EF7_ESP_SP (spoofer temporarily removed) Optimization.
#EF7_ESP_SP (spoofer temporarily removed) Fixed & updated.
#EF7_ESP_SP (spoofer temporarily removed) Frozen for fix.
#PYBG_ESP #PYBG_FULL Updated.
#EF7_ESP_SP (spoofer temporarily removed) Updated. + 48h.
#PYBG_ESP #PYBG_FULL Frozen for update.
#EF7_ESP_SP (spoofer temporarily removed) Frozen for update.
#PYBG_ESP #PYBG_FULL Updated.
#PYBG_ESP #PYBG_FULL Frozen for fix.
#D3adByD4yl1ghtSP Fixed skillcheck.
#Armo3 Skeleton fixes.
Showing the 12 most recent of 20 posts we hold for @softhubdev. 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 12 October 2026 — this entry's latest reading, not the date you are reading this.
“Soft[HUB]” (@softhubdev), 612 subscribers as measured 12 October 2026. Telegram Register, tgregister.com/channel/softhubdev.
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.