Channel
@ddi_i6969
On this record: Topic · Growth · Engagement · Reactions · Posts · Citations · Cite this entry
377subscribers
+269 since we began measuring on 11 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1003829099561 |
|---|---|
| Type | Channel |
| Username | @ddi_i6969 |
| Created | 9 August 2026 — measured — dated from the channel’s first post |
| First recorded | 11 August 2026 |
| Last confirmed live | 18 September 2026 |
| Measurements held | 8 |
| Confirmed unchanged | 1 time, most recently 18 September 2026 |
| On Telegram | t.me/ddi_i6969 |
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B-FP8, prompt version 1) read this channel’s own recent posts on 22 September 2026 and assigned it the closest of 31 fixed categories, at 90% confidence. This is a model’s judgement about what the channel is likely to be about, not a fact this register measured the way a subscriber count or a view count is measured — it can be revised on a later pass, and it carries no weight anywhere else on this page. How this classification works, and why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 18 Sept 2026, 12:15 | 377 | +10 |
| 11 Sept 2026, 03:18 | 367 | +18 |
| 2 Sept 2026, 05:43 | 349 | +61 |
| 25 Aug 2026, 05:06 | 288 | +122 |
| 19 Aug 2026, 03:56 | 166 | +53 |
| 12 Aug 2026, 13:05 | 113 | +5 |
| 11 Aug 2026, 21:30 | 108 | no change |
| 11 Aug 2026, 21:21 | 108 | first reading |
5 posts held, back to 9 August 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 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 5 posts for this entry, the most recent from 10 August 2026. An engagement rate over an empty window would be a number about nothing.
102 reactions across 3 posts, in 12 distinct kinds. The most used accounts for 20.6% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| custom 5359562050840331910 | 21 | 20.6% | |
| custom 5361648618967168747 | 15 | 14.7% | |
| 🍓 | 15 | 14.7% | |
| custom 5418170740769847653 | 13 | 12.7% | |
| ❤ | 11 | 10.8% | |
| custom 5296785335668202877 | 9 | 8.82% | |
| custom 5402449468249371040 | 8 | 7.84% | |
| custom 5361651784358064483 | 4 | 3.92% | |
| custom 5361727221163654852 | 3 | 2.94% | |
| 👻 | 1 | 0.98% | |
| 💋 | 1 | 0.98% | |
| 💘 | 1 | 0.98% |
Custom emoji. 7 of the rows above are Telegram custom emoji, which the public preview renders as an element carrying only a numeric id — no character, and no image we can reach. The id is printed as-is rather than substituted with a look-alike glyph, because a stand-in would be our invention showing where a measurement should be. The counts beside them are Telegram’s.
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 3 of the 5 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 102 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 5 most recent posts we hold, published 9 August 2026 to 10 August 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.
директ…..
custom 535956205084033191016custom 54024494682493710405custom 52967853356682028772👻1custom 53616486189671687471custom 53616517843580644831custom 53617272211636548521custom 54181707407698476531
Posted without readable text
комментарии.
custom 536164861896716874712custom 52967853356682028775custom 54181707407698476535custom 53595620508403319101custom 53616517843580644831custom 53617272211636548521custom 54024494682493710401
Photo, posted without a caption
🍓15❤11custom 54181707407698476537custom 53595620508403319104custom 52967853356682028772custom 53616486189671687472custom 53616517843580644832custom 54024494682493710402
Channel created
Showing the 5 most recent of 5 posts we hold for @ddi_i6969. 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.
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.
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 18 September 2026 — this entry's latest reading, not the date you are reading this.
“софа убийца смерти 2007.” (@ddi_i6969), 377 subscribers as measured 18 September 2026. Telegram Register, tgregister.com/channel/ddi_i6969.
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.