Telegram RegisterThe public register of Telegram
Telegram profile photo for TR ++

Supergroup

TR ++

@TechRabbits

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

7,848members

-177 since we began measuring on 23 August 2026

1,515 online right now

Risers and fallers across the register · movement among entries of 3,162–10,000.

Register entry

Telegram ID-1001112614954
TypeSupergroup
Username@TechRabbits
Created5 April 2017measured — cross-checked against a third-party dataset (ext.tg_channel)
First recorded25 August 2026
Last confirmed live2 September 2026
Measurements held6
Confirmed unchanged1 time, most recently 2 September 2026
On Telegramt.me/TechRabbits

Growth

7,8488,0257,936.523 August 2026 — 8,025 members24 August 2026 — 8,003 members25 August 2026 — 8,003 members27 August 2026 — 7,961 members30 August 2026 — 7,894 members2 September 2026 — 7,848 members23 August 20262 September 2026
6 measurements spanning 10 days, net -177. 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 7,821–8,052 and does not start at zero.
Measurement log — every members count we have recorded
Measured (UTC)MembersChange
2 Sept 2026, 11:047,848-46
30 Aug 2026, 18:547,894-67
27 Aug 2026, 15:257,961-42
25 Aug 2026, 20:258,003no change
24 Aug 2026, 23:348,003-22
23 Aug 2026, 19:158,025first reading

Engagement

No public post preview. We read this entry on 25 August 2026 and Telegram serves no public post stream for it — the channel has previews switched off, or it is a group or bot with no readable feed. Views, reactions and engagement rates cannot be measured from the outside for an entry in this state, so we publish none. Subscriber counts above are unaffected.

Forward network

Republished by

Channels on the register that have forwarded this channel's posts into their own feed.

Built only from forwarded posts we have actually read, on both sides. Coverage is early and deliberately incomplete: a missing link means we have not read the post that would prove it, never that the relationship does not exist. Counts are distinct forwarded posts observed, so they only ever go up as we read more.

Mentions

Named by 1 registered channel — every channel on the register whose own posts have named this one, by its current username or any other username it currently holds, merged from two separately captured readings of the same fact so a namer caught by only one of them is not missed and a namer both caught is not counted twice. A username this channel has since dropped is not matched — that handle may belong to someone else now, and crediting today’s namer to yesterday’s owner would misattribute it.

Named by

Channels on the register whose posts name this channel's handle.

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

“TR ++” (@TechRabbits), 7,848 members as measured 2 September 2026. Telegram Register, tgregister.com/channel/TechRabbits.

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.