Channel
@moddychat_cube_net
On this record: Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Cite this entry
4subscribers
+0 since we began measuring on 10 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1002979124288 |
|---|---|
| Type | Channel |
| Username | @moddychat_cube_net |
| Description | if you obey I might give you a treat <3 привязан к @cube_net |
| Created | Between 1 August 2025 and 31 October 2025— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 13 August 2026 |
| Last confirmed live | 17 August 2026 |
| Measurements held | 2 |
| On Telegram | t.me/moddychat_cube_net |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 04:48 | 4 | no change |
| 10 Aug 2026, 02:47 | 4 | first reading |
20 posts held, back to 14 February 2026 — 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 20 posts for this entry, the most recent from 7 April 2026. An engagement rate over an empty window would be a number about nothing.
Lifetime counters from Telegram’s own channel header, read 13 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.
20 reactions across 20 posts, in 3 distinct kinds. The most used accounts for 45.0% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| ⚡ | 9 | 45.0% | |
| ❤ | 6 | 30.0% | |
| 🔥 | 5 | 25.0% |
No sentiment is inferred, and none should be read in. This table is ordered by count and by nothing else. Emoji do not carry stable meaning across languages or communities — 🙏 is thanks in one channel and mourning in another — so we publish which ones were pressed and how often, and pass no judgement on what an audience meant by them.
Precision. Telegram publishes reaction counts per emoji and short-forms each one — 4.34K, 1.2M — so any single kind at or above 1,000 reaches us at three significant figures, and only counts below 1,000 are exact. The shares above are ratios of those figures and carry the same error. This is also why the total here can differ slightly from a reaction total printed elsewhere on the page: both are sums of the same rounded parts, taken over samples with different edges.
Coverage. Reactions were read on 20 of the 20 sampled posts in this sample. Summed by Telegram’s own count on each post — not by adding up the per-emoji breakdown above — those same posts carry 20reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 20 most recent posts we hold, published 14 February 2026 to 7 April 2026, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ меня вообще ничего не беспокоит, не знаю, с чего ты это взял. я предупрежу, если будет острая необходимость—если у меня, не знаю, появятся провалы в памяти или что-нибудь. я знаю, что делаю. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
❤1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ ха??? пока что я могу себя контролировать, а других ситуаций с похожим исходом я не представляю. так что и думать об этом незачем. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
⚡1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ это снова касалось Его. и некоторых определенных личностей, не буду показывать пальцем. насчет всего остального догадаться несложно. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
🔥1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ нет, не совсем. просто странный сон, который я ощутил слишком реально. мне не понравилось, не хотел бы так снова. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
❤1
ㅤ ЗАПИСЬ #25 📝 ╭──╯ . . . . . ㅤс добрым ...? ого, да неважно. даже не знаю, чем это объяснить... ㅤну, хотя бы небо красивое. всё равно я не смогу уснуть в ближайшее время. ㅤно, знаете? мне кажется, люди очень схожи со звездами. маленькие с первого взгляда, но при этом яркие и неоспоримо важные. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
⚡1
ㅤ ЗАПИСЬ #24 📝 ╭──╯ . . . . . ㅤдумаю, мне стоит пересмотреть рацион того, что я ем. сегодня весь день тошнит, а я даже понять не могу от чего, ну что за дела. то одно, то другое... ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
⚡1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ . . . ужас. достаточно для того, чтобы стоять на своих ногах. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
❤1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ да нет же! что ж такое. какое старение, я еще полон сил. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
⚡1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ чего??? мне еще не 60 лет, спасибо огромное. ㅤпочему болит — не знаю. может, на смену погоды. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
❤1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ это точно. я бы спал и спал, но всё же для нормального функционирования нужно вставать, иногда. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
⚡1
ㅤ ЗАПИСЬ #23 📝 ╭──╯ . . . . . ㅤэто кошмар какой-то, с приходом весны у меня всё время болит голова. раньше такого никогда не было, джекпот прямо. ㅤа у вас как дела? вдруг я не один такой везучий.. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
❤1
ㅤ ОТВЕТ 📨 ╭──╯ . . . . . ㅤ пока что сомневаюсь. у меня на базе и так кто только не живет, пусть и не на постоянной основе. ㅤㅤㅤㅤㅤㅤ . . . . . ╰──╮
⚡1
Showing the 12 most recent of 20 posts we hold for @moddychat_cube_net. 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.
Citation-graph rank — 1,020,276 of 1,548,671entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.
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.
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 13 August 2026 — this entry's latest reading, not the date you are reading this.
“записи Модди.” (@moddychat_cube_net), 4 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/moddychat_cube_net.
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.