4 Jun 2018, 13:12 UTCviews —
Render Token RNDR pinned «This is a place holder account. Find the official channel at https://t.me/rendertoken»
Channel
Render Token RNDR
@RenderTokenOfficial
On this record: Growth · Engagement · Posts · Citations · Cross-platform identity · Cite this entry
457subscribers
-7 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 | -1001211731054 |
|---|---|
| Type | Channel |
| Username | @RenderTokenOfficial |
| Created | 4 June 2018 — measured — dated from the channel’s first post |
| First recorded | 8 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 4 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/RenderTokenOfficial |
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 18:08 | 457 | -6 |
| 8 Aug 2026, 04:48 | 463 | no change |
| 8 Aug 2026, 04:12 | 463 | -1 |
| 7 Aug 2026, 11:13 | 464 | first reading |
Engagement
4 posts held, back to 4 June 2018 — 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.
Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 4 posts for this entry, the most recent from 4 June 2018. An engagement rate over an empty window would be a number about nothing.
Recent posts
4 Jun 2018, 13:12 UTC≈5,870 viewsread 8 August 2026
This is a place holder account. Find the official channel at https://t.me/rendertoken
4 Jun 2018, 13:12 UTCviews —
Channel name was changed to «Render Token RNDR»
4 Jun 2018, 13:09 UTCviews —
Channel created
Showing the 4 most recent of 4 posts we hold for @RenderTokenOfficial. 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.
Cross-platform identity — Wikidata
A Wikidata item names this Telegram handle as belonging to the entity it describes. This is Wikidata’s claim, not a verification made by this register — nobody here confirmed that the account is genuinely operated by the entity named. Wikidata content is CC0; every fact below is dated to when it was read from Wikidata, not to when the association was first made there.
| Label | RNDR |
|---|---|
| Description | RNDR Network Blockchain and token platform |
| X / Twitter | @rendertoken |
| Official site | https://rendertoken.com |
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 16 August 2026 — this entry's latest reading, not the date you are reading this.
“Render Token RNDR” (@RenderTokenOfficial), 457 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/RenderTokenOfficial.
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.