24 Month + emerald Nitro - Created in 2016 - Pb test accept - Oge (outlook.com) - 50+ decos - clean account with 0 ticket - with 1 year nitro C/o 200$ Bin 250$ DM @slayercentral or @nexaogu Middleman accept

Channel
Bots Community™
@programmerhq
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
234subscribers
+0 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 | -1002018569967 |
|---|---|
| Type | Channel |
| Username | @programmerhq |
| Created | Between 1 November 2023 and 31 May 2024— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 8 August 2026 |
| Last confirmed live | 8 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/programmerhq |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Aug 2026, 10:03 | 234 | no change |
| 7 Aug 2026, 17:53 | 234 | first reading |
Engagement
17 posts held, back to 30 August 2025 — 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 pageof Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 30.3%
- avg views ÷ 234 subscribers
- Avg views / post
- 71.0
- 2 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 2
- of 17 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.
| Window | Rolling 30 days · latest post in window 21 July 2026 |
|---|---|
| Posts held | 17 (30 August 2025 – 21 July 2026) |
| Views total | 142 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 8 Aug 2026, 10:03 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.
What this channel posts
- Photos
- 45
- Videos
- 1
- Links
- 7
Lifetime counters from Telegram’s own channel header, read 8 August 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
24 Month + emerald Nitro - Created in 2016 - Pb test accept - Oge (outlook.com) - 50+ decos - clean account with 0 ticket - with 1 year nitro C/o 200$ Bin 250$ DM @slayercentral or @nexaogu Middleman accept
april fools 😭
@everyone It’s now been officially revealed Discord is removing all profile badges starting next month and bringing back discriminators (the classic #0001 tags) to combat the massive buying/selling market. After years of HypeSquad houses, Early Supporter, Bug Hunter, Partner, Bot Developer and all the other badges… they’re all getting wiped. Thank you to everyone who built, collected, traded, and hyped the Discord …
HypeSquad Manager is now live. Switch your Discord HypeSquad badge between Bravery, Brilliance, and Balance instantly. Remove your badge with one click. Paste your token, pick a house, done. Your token is processed server-side and never stored. https://hypesquad.cybx.space/
Buying Booster Badges ▸ Must be OGE ▸ Any Trusted MM Accepted DM @notherhacker or @nexaogu
if anyone have bb with oge then dm me
sxld
timewasters don't dm
BUYING DISCORD MARKETPLACE LIST DM IF YOU HAVE @nexaogu
SELLING VERIFIED DISCORD SERVER (RARE) INFO : • ALL ARE LEGIT MEMBERS [ NO BOTTED / FAKE MEMBERS ] • FULLY LEGIT GROWTH SERVER • ALL VANITY JOINS NOTES : • VERIFICATION / PARTNER IS CLOSED SINCE LAST 3 YEARS [ NO ONE HAS VERFIED SERVER IN MARKET SOO VERY RARE ] • SERVER OWNERSHIP WILL TRANSFER ON YOUR ACCOUNT [ MUST HAVE BUSINESS MAIL ] • ALL REAL MEMBERS • VERFIED SERVER ☑️ • NOT GOING TO DISCLOSE ANY DETAILS A…
All real dm @mandhir_sawarn to buy
Showing the 12 most recent of 17 posts we hold for @programmerhq. 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.
Handles this channel named that no longer answer
- Dead references
- 2
- handles named in this channel’s posts, vacant today
- Evidenced gone
- 0
- we ourselves saw one of these resolve, at some point
- Never seen alive
- 2
- vacant every time we have ever looked
@programmerhq named 2 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
Never seen alive
References a handle that is not a live channel — we have no record it ever was one.
named in 3 posts, 9 August 2026 – 9 August 2026
named in 1 post, 9 August 2026 – 9 August 2026
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 August 2026 — this entry's latest reading, not the date you are reading this.
“Bots Community™” (@programmerhq), 234 subscribers as measured 8 August 2026. Telegram Register, tgregister.com/channel/programmerhq.
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.