Channel
@Graphene_RU
On this record: Growth · Engagement · Posts · Citations · Cite this entry
254subscribers
+2 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001084018179 |
|---|---|
| Type | Channel |
| Username | @Graphene_RU |
| Created | 19 April 2017 — measured — cross-checked against a third-party dataset (ext.tg_channel) |
| First recorded | 7 August 2026 |
| Last confirmed live | 16 September 2026 |
| Measurements held | 5 |
| Confirmed unchanged | 2 times, most recently 16 September 2026 |
| On Telegram | t.me/Graphene_RU |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 8 Sept 2026, 15:16 | 254 | -1 |
| 23 Aug 2026, 13:24 | 255 | +2 |
| 15 Aug 2026, 00:22 | 253 | +1 |
| 7 Aug 2026, 02:17 | 252 | no change |
| 6 Aug 2026, 00:38 | 252 | first reading |
20 posts held, back to 14 December 2023 — 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 20 posts for this entry, the most recent from 3 August 2026. An engagement rate over an empty window would be a number about nothing.
Soft launch: GOLD BUG GOLD BUG это приложение на Graphene DEX для прогнозов по Gold/Silver Ratio. • Прогноз по цене золота, измеренной в серебре. • Открываете позицию на рост или падение пары. • Прибыль и убыток считаются в GOLD. • Комиссии оплачиваются в GPH. • Сделки проходят через Graphene DEX. 🧪 Сейчас работает TEST GOLD это тестовая среда, не реальные деньги. Если вы пользуетесь Graphene, RuDEX или другими п…
Портал тикетов поддержки переезжает на новую платформу, в связи с изменениями условий обслуживания компании freshdesk Новый сервис для тикетов шлюза RUDEX: https://rudex.zohodesk.eu/
Шлюзы BEP20 (BNB, BTCB) функционируют и открыты для автоматического ввода/вывода
Шлюзы BEP20 (BNB, BTCB) закрыты на обслуживание
Шлюзы BEP20 (BNB, BTCB) и XMR функционируют и открыты для автоматического ввода/вывода
Шлюзы BEP20 (BNB, BTCB) и XMR закрыты на обслуживание
Уважаемые пользователи RUDEX! Сообщаем вам, что 1 марта 2026 года в связи с низким объёмом торгов токены EOS, STEEM, DEC, SPS и BTS будут перманентно удалены с биржи RUDEX. - Начиная с 12 февраля 2026 года депозиты в EOS, STEEM, DEC, SPS и BTS будут недоступны. - Торговые операции с токенами EOS, STEEM, DEC, SPS и BTS будут окончательно остановлены 1 марта 2026 года. - Пожалуйста, выведите все средства в токенах EO…
Шлюзы BEP20 (BNB, BTCB, DEC, SPS) функционируют и открыты для автоматического ввода/вывода
Шлюзы BEP20 (BNB, BTCB, DEC, SPS) закрыты на обслуживание
Для токена PZM стали доступны следующие рынки: PZM/XMR PZM/GPH PZM/USDT PZM/gpUSD PZM/gpEUR PZM/gpRUB PZM/gpGOLD PZM/gpSILVER
Шлюз PZM функционирует и открыт для автоматического ввода/вывода
Шлюзы BEP20 (BNB, BTCB, DEC, SPS) функционируют и открыты для автоматического ввода/вывода
Showing the 12 most recent of 20 posts we hold for @Graphene_RU. 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.
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.
Named by 2 registered channels — 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.
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.
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 September 2026 — this entry's latest reading, not the date you are reading this.
“Graphene hub (RUDEX updates)” (@Graphene_RU), 254 subscribers as measured 8 September 2026. Telegram Register, tgregister.com/channel/Graphene_RU.
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.