Telegram RegisterThe public register of Telegram
Telegram profile photo for TGlux |[Information]

Channel

TGlux |[Information]

@tglux

On this record: Growth · Engagement · Posts · Cite this entry

401subscribers

+7 since we began measuring on 6 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1002941300375
TypeChannel
Username@tglux
CreatedBetween 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded6 August 2026
Last confirmed live25 August 2026
Measurements held5
Confirmed unchanged1 time, most recently 25 August 2026
On Telegramt.me/tglux

Growth

394401397.56 August 2026 — 394 subscribers6 August 2026 — 394 subscribers12 August 2026 — 396 subscribers18 August 2026 — 397 subscribers25 August 2026 — 401 subscribers6 August 202625 August 2026
5 measurements spanning 19 days, net +7. 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 393–402 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
25 Aug 2026, 13:56401+4
18 Aug 2026, 21:22397+1
12 Aug 2026, 20:53396+2
6 Aug 2026, 19:52394no change
6 Aug 2026, 02:12394first reading

Engagement

20 posts held, back to 19 April 2026the 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.

ERR · 30 days
60.8%
avg views ÷ 401 subscribers
Avg views / post
244
1 post measured
Reaction rate
this channel exposes no reaction counts
Posts in window
1
of 20 held

ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.

ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 August 2026
Posts held20 (19 April 20262 August 2026)
Views total244
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken6 Aug 2026, 19:52 UTC

Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.

Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.

Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.

Recent posts

2 Aug 2026, 19:19 UTC244 viewsread 6 August 2026

[API] 📢 Update The Cancel Request feature has been added to the API bot. You can now request order cancellations using: /cancel 1234 or /cancel 1234,1234 Once your request is approved by an admin, you'll automatically receive a notification and the refunded amount will be added back to your balance. bot : @TGluxApiBot

Signed 𝙽𝚊𝚓𝚒

29 Jul 2026, 16:38 UTC333 viewsread 6 August 2026

Unfortunately, Telegram has once again started a new wave of account freezes since last night. As a result, we have lost approximately half of our account capacity, and the remaining accounts are currently handling all active orders. Because of this, some orders may take longer than usual to complete. Our team is working around the clock to restore full capacity and return all services to normal as quickly as possi

Signed 𝙽𝚊𝚓𝚒

24 Jul 2026, 18:02 UTC376 viewsread 6 August 2026

⚠️⚠️ Telegram Ads services have been permanently removed from both the bot and the API.

Signed 𝙽𝚊𝚓𝚒

14 Jul 2026, 11:32 UTC500 viewsread 6 August 2026

✅ Update: The entire panel has been migrated to the new telegram.me format. All services now fully support https://telegram.me/... links.

Signed 𝙽𝚊𝚓𝚒

14 Jul 2026, 08:41 UTC688 viewsread 6 August 2026

📢 Important Update Due to the recent changes affecting Telegram’s t.me domain, please use the new telegram.me links when submitting new orders. Old format: ❌ https://t.me/... New format: ✅ https://telegram.me/... Example: https://telegram.me/iNaji Using the new format will help ensure your orders are processed correctly while the issue with t.me is being resolved.

Signed 𝙽𝚊𝚓𝚒

14 Jul 2026, 08:28 UTC602 viewsread 6 August 2026
Photo

📢 Important Service Notice Due to a global issue affecting Telegram’s t.me domain, many Telegram-related services are currently experiencing disruptions. The t.me domain has temporarily become unavailable, causing problems with Telegram links, channel access, and services that rely on these links. As a result, some of our services may be delayed or temporarily unavailable until Telegram fully resolves the issue.

Signed 𝙽𝚊𝚓𝚒

23 Jun 2026, 03:47 UTC437 viewsread 6 August 2026

If you have any issues with the services, please contact us via private message or through the channel’s direct messages. @iNaji Channel Direct

Signed 𝙽𝚊𝚓𝚒

21 Jun 2026, 01:27 UTC468 viewsread 6 August 2026

📣 Service Update ✅ Our servers have been upgraded, and a large number of accounts have been added to the View and other related services. As a result, order completion speeds have increased significantly. ✅ In some cases, there were issues with orders delivering fewer than expected. We believe this issue has now been resolved following the latest updates. ✅ All issues related to Post Share services have been fully

Signed 𝙽𝚊𝚓𝚒

16 Jun 2026, 18:49 UTC353 viewsread 6 August 2026

The capacity of both 3-month member services has been increased.

Signed 𝙽𝚊𝚓𝚒

15 Jun 2026, 12:38 UTC381 viewsread 6 August 2026

We are currently updating the panel. Your orders may be completed with some delay during this time. Thank you for your patience.

Signed 𝙽𝚊𝚓𝚒

29 May 2026, 11:46 UTC470 viewsread 6 August 2026

The capacity of both member services, 165 and 831, has been increased.

Signed 𝙽𝚊𝚓𝚒

29 May 2026, 00:52 UTC500 viewsread 6 August 2026

This offer won’t be repeated again, so make the most of it while you can. Users who use the bot and place high-volume orders can message us to get a custom discount set for their account.

Signed 𝙽𝚊𝚓𝚒

Showing the 12 most recent of 20 posts we hold for @tglux. 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 25 August 2026 — this entry's latest reading, not the date you are reading this.

“TGlux |[Information]” (@tglux), 401 subscribers as measured 25 August 2026. Telegram Register, tgregister.com/channel/tglux.

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.