Telegram RegisterThe public register of Telegram
Telegram profile photo for Hub Net

Channel

Hub Net

@Hubnet1

On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry

87subscribers

+5 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-1003798264551
TypeChannel
Username@Hubnet1
Created10 June 2026 — measured — dated from the channel’s first post
First recorded9 August 2026
Last confirmed live8 October 2026
Measurements held9
Confirmed unchanged1 time, most recently 8 October 2026
On Telegramt.me/Hubnet1

Topic

Other / unclassifiable — 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 27 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

7787827 August 2026 — 82 subscribers9 August 2026 — 82 subscribers15 August 2026 — 79 subscribers22 August 2026 — 77 subscribers30 August 2026 — 83 subscribers9 September 2026 — 85 subscribers15 September 2026 — 87 subscribers28 September 2026 — 86 subscribers8 October 2026 — 87 subscribers7 August 20268 October 2026
9 measurements spanning 62 days, net +5. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 76–89 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
8 Oct 2026, 13:0087+1
28 Sept 2026, 15:5586-1
15 Sept 2026, 18:0187+2
9 Sept 2026, 02:5685+2
30 Aug 2026, 17:0783+6
22 Aug 2026, 22:1677-2
15 Aug 2026, 11:5679-3
9 Aug 2026, 18:1682no change
7 Aug 2026, 19:3782first reading

Engagement

8 posts held, back to 10 June 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 8 posts for this entry, the most recent from 22 July 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

6 reactions across 1 post, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
❤6100.0%

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 3 of the 8 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 6 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 8 most recent posts we hold, published 10 June 2026 to 22 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.

Recent posts

22 Jul 2026, 10:16 UTC360 views6 reactionsread 9 August 2026
File

🔥100 گیگ کانفیگ رایگان برای اعضایHUB NET 💎به پاس همراهی شما عزیزان 💎 🌟100 گیگ کانفیگ رایگان سریعا هر چقدر دانلود دارید بزنید 🔼ری اکشنو بترکونید تا انرژی بگیرم بیشتر براتون کانفیگ رایگان بزارم ❤️بچه ها برای دوستانتون بفرستین کانفیگ ها رو 🔓رمز کانفیگ : hubnet1 📣تنها کانال رسمی ما : 📣@Hubnet1 🛒خرید سریع از ربات: 🤖@viphubnet_bot 💬پشتیبانی ۲۴ ساعته: 👨‍💻@Suphubnet

❤6

7 Jul 2026, 08:19 UTC212 viewsread 9 August 2026

🎁اول تست رایگان بگیر ، بعد با خیال راحت خرید کن ! 💎هنوز مطمئن نیستی؟ اول کیفیت HUB NET رو رایگان امتحان کن، بعد با خیال راحت خریدت رو انجام بده. 🚀 🛡 تست رایگان ⚡️ لوکیشن‌های پرسرعت: 🇩🇪🇺🇸🇫🇮🇹🇷🇦🇺🇨🇦 🔓 سرعت بالا | امنیت بالا | اتصال پایدار 📬 برای دریافت تست رایگان، همین الان وارد ربات شوید . 📣تنها کانال رسمی ما : 📣@Hubnet1 🛒خرید سریع از ربات: 🤖@viphubnet_bot 💬پشتیبانی ۲۴ ساعته: 👨‍💻@Suphubnet

5 Jul 2026, 20:19 UTC151 views0 reactionsread 9 August 2026

💡معرفی و نحوه ی اتصال • 🔹برنامه ی V2rayNg مناسب اندروید و ویندوز 🔗 دیدن آموزش و لینک برنامه ( اینجا کلیک کنید ) • 🔹برنامه ی Happ مناسب اندروید و آیو اس [ آیفون ] 🔗 دیدن آموزش و لینک برنامه ( اینجا کلیک کنید ) •🔹 برنامه ی V2ray Tun مناسب اندروید و آیو اس [ آیفون ] 🔗دیدن آموزش و لینک برنامه ( اینجا کلیک کنید ) 🔹برنامه ویندوز و مک نیز می‌توانید از برنامه های V2rayNg- v2raytun و سایر استفاده کنید  🛒 جهت تست…

5 Jul 2026, 17:22 UTC441 viewsread 9 August 2026

🎉 کد تخفیف ویژه HUB NET 🌟وقتشه با هزینه کمتر، اینترنتی سریع و امن رو تجربه کنی! 🎁کد تخفیف: HUB20 🛡 ۲۰٪ تخفیف روی خرید اشتراک ⌛️ اعتبار به مدت ۳ روز ⚡️ لوکیشن‌های پرسرعت: 🇩🇪🇺🇸🇫🇮🇹🇷🇦🇺🇨🇦 🔓 سرعت بالا | امنیت بالا | اتصال پایدار 📬 برای ثبت سفارش، کد تخفیف را هنگام خرید در ربات وارد کنید. 📣تنها کانال رسمی ما : 📣@Hubnet1 🛒خرید سریع از ربات: 🤖@viphubnet_bot 💬پشتیبانی ۲۴ ساعته: 👨‍💻@Suphubnet

5 Jul 2026, 08:33 UTC346 views0 reactionsread 9 August 2026
Photo

🔹هاب نت | وقتی سرعت و پایداری برات مهمه 💎اتصالی سریع، امن و بدون محدودیت اگر کیفیت اتصال برایتان مهم است، وقت آن رسیده که تفاوت را تجربه کنید. 🔗اتصال با تمام اپراتور ها🛜🛜🛜🛜 🌐دارای لوکیشن های 🇩🇪🇺🇸🇫🇮🇹🇷🇦🇺🇨🇦 ⚡️سرعت فوق‌العاده و پینگ پایین 🔒 امنیت بالا و حفظ حریم خصوصی 🌐 سرورهای پرسرعت در کشورهای مختلف 📡 اتصال پایدار و بدون قطعی 🕯ایپی ثابت برای ترید و صرافی و بانک های شما 🎮 مناسب گیم، استریم،اینستاگرام، ت…

Showing the 8 most recent of 8 posts we hold for @Hubnet1. 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.

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 8 October 2026 — this entry's latest reading, not the date you are reading this.

“Hub Net” (@Hubnet1), 87 subscribers as measured 8 October 2026. Telegram Register, tgregister.com/channel/Hubnet1.

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.