Telegram RegisterThe public register of Telegram
Telegram profile photo for ժׁׅׅ݊꯱ꩇׁׅ֪݊ꪱׁׁׁׅׅׅ݊ꪀtׁׅ ܻ⨍ᥣׁׅ֪ᨵׁׅׅᨵׁׅׅժׁׅ݊

Channel

ժׁׅׅ݊꯱ꩇׁׅ֪݊ꪱׁׁׁׅׅׅ݊ꪀtׁׅ ܻ⨍ᥣׁׅ֪ᨵׁׅׅᨵׁׅׅժׁׅ݊

@dsmint_flood

On this record: Growth · Engagement · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry

19subscribers

+4 since we began measuring on 12 August 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003855166715
TypeChannel
Username@dsmint_flood
Created24 July 2026measured — dated from the channel’s first post
First recorded12 August 2026
Last confirmed live11 September 2026
Measurements held5
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/dsmint_flood

Growth

15191712 August 2026 — 15 subscribers13 August 2026 — 15 subscribers21 August 2026 — 16 subscribers2 September 2026 — 18 subscribers11 September 2026 — 19 subscribers12 August 202611 September 2026
5 measurements spanning 30 days, net +4. 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 14–20 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 05:1719+1
2 Sept 2026, 09:4418+2
21 Aug 2026, 04:4316+1
13 Aug 2026, 07:3515no change
12 Aug 2026, 11:0315first reading

Engagement

17 posts held, back to 24 July 2026the 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 17 posts for this entry, the most recent from 6 August 2026. An engagement rate over an empty window would be a number about nothing.

Reaction mix

8 reactions across 6 posts, in 1 kind.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
custom 53999418558885645388100.0%

Custom emoji. One row above is a 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 count beside it is 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 7 of the 17 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 8 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 17 most recent posts we hold, published 24 July 2026 to 6 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.

Recent posts

6 Aug 2026, 15:45 UTC30 viewsread 12 August 2026
Forwarded from @kellyinfow

⭐ 🤩🤍𝐚𝕥𝗍𝐥𝖾 🤍𝐥𝕕'𝐬🤍 приз-15 ⭐️ для участия:❓ 1. подписка на инфо. 2. 1/3 рк. 3. репост в инфо канал 4. инфо, аву и + в комм. места-0/13

3 Aug 2026, 01:31 UTC53 viewsread 12 August 2026
Forwarded from @Vlamixx_floodVideo

🍏🍏🍏🍏 ➿➿➿🍏🍏🍏🍏🍏 Как вступить: 1. Подписаться на инфо 2. Поставить реакцию, если у вас прем то поставьте 3 реакций. 3. Сделайте сзрп на свой инфо 4. Поставьте аву инфо и сам @ в комментариях !Участвовать могут не только наши Сз! 2/20 #сзрп #Vlamixx_rp + участие по желанию

1 Aug 2026, 14:19 UTC61 views2 reactionsread 12 August 2026
Photo

υׁׅ݊ꪀꪱׁׁׁׅׅׅᨵׁׅׅ݊ꪀ ꭈׁׅυׁׅᥣׁׅ֪ꫀׁׅܻׅ݊꯱ подписка: 1:1 пост: без разницы рп держим 1 день ➿➿➿➿➿➿➿➿➿➿ почему мы можем с вами разорвать союз? О1: обзывательство в наш флуд О2: закрытие О3: долгий рест

custom 53999418558885645382

1 Aug 2026, 06:14 UTC67 viewsread 12 August 2026

у нас появился лайф канал. там будут все важные посты и видео !

1 Aug 2026, 05:58 UTC57 views0 reactionsread 12 August 2026
Forwarded from @hinteriflood_infoPhoto

🤩ᖯִ𐐼ִt𝘁l 𝗳𝗹𑄝ֺ𑄝ֺ𝗱𝘀📞 ➿➿ . ➿➿. ➿➿ Дᴧя учᴀᴄᴛия ʙ ᴋᴏʍʍᴇнᴛᴀᴩии нужнᴏ ᴄᴋинуᴛь — быᴛь ᴨᴏдᴨиᴄᴀнныʍ нᴀ нᴀᴄ и ᴄᴋинуᴛь ᴨᴩуɸ — ᴄдᴇᴧᴀᴛь ᴩᴇᴨᴏᴄᴛ ʙ ᴄʙᴏё инɸᴏ и ᴄᴋинуᴛь ᴨᴩуɸ — ᴀʙу ᴄʙᴏᴇᴦᴏ ɸᴧудᴀ и инɸᴏ — ᴄдᴇᴧᴀᴛь ᴩᴇᴨᴏᴄᴛ ʙ инɸᴏ ➿➿ . ➿➿. ➿➿ 📞ᎡֹυІᧉઠׅ🎀 — нᴀᴋᴩуᴛᴋᴀ ᴄᴛᴩᴏᴦᴏ ɜᴀᴨᴩᴇщᴇнᴀ — ᴏᴄᴋᴏᴩбᴧᴇниᴇ ɸᴧудᴏʙ, учᴀᴄᴛниᴋᴏʙ и ᴀдʍиниᴄᴛᴩᴀции ɜᴀᴨᴩᴇщᴇнᴀ — ᴄᴨᴀʍ ɜᴀᴨᴩᴇщᴇн — бᴏᴧьɯᴇ 15 ɜʙᴇɜд ᴋидᴀᴛь ʙ @truprincess90 — ɜʙᴇɜды ᴨᴏᴄᴧᴇ бᴀᴛᴧᴀ нᴇ ᴨᴩинᴀдᴧᴇжᴀᴛь ʙᴏ

31 Jul 2026, 15:55 UTC59 views1 reactionsread 12 August 2026
Photo

ꪱׁׁׁׅׅׅ݊ꪀꪱׁׁׁׅׅׅtׁׁׅׅꪱׁׁׁׅׅׅɑׁׅᥣׁׅ֪ мы никого не заставляем ставить инитиал в ник,это ваше желание ставить или нет ! ᵒʷⁿ ᵈˢᵐᶦⁿᵗ ( незя) ᶜᵒ ᵒʷⁿ ᵈˢᵐᶦⁿᵗ ( тоже низя ) 🖤🖤🖤🖤🖤🖤🖤 ˡᵒᵛᵉ ᵈˢᵐᶦⁿᵗ ᵃᵈᵐᶦⁿ ᵈˢᵐᶦⁿᵗ ᵒˡᵈ ᵈˢᵐᶦⁿᵗ ⁿᵉʷ ᵈˢᵐᶦⁿᵗ ᵈˢᵐᶦⁿᵗ ᵐᵉᵐᵇᵉʳ ᵈˢᵐᶦⁿᵗ ᵇᵉˢᵗ ᵈˢᵐᶦⁿᵗ or ᵈ³⁸ / ⁶³⁸ копируется при нажатии !

custom 53999418558885645381

31 Jul 2026, 15:55 UTC56 viewsread 12 August 2026
Photo

℘ɑׁׅ݊ꪀtׁׅꫀׁׅܻ݊tׁׅ с 2O26.O8.31 название «dsmint» полностью принадлежит нам. если мы увидим флуд,кф,канал,профиль с таким названием мы имеем полное право попросить поменять название. если человек будет отказыватся менять название мы будем принимать серьёзные меры.

Showing the 12 most recent of 17 posts we hold for @dsmint_flood. 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.

Forward network

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

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

“ժׁׅׅ݊꯱ꩇׁׅ֪݊ꪱׁׁׁׅׅׅ݊ꪀtׁׅ ܻ⨍ᥣׁׅ֪ᨵׁׅׅᨵׁׅׅժׁׅ݊” (@dsmint_flood), 19 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/dsmint_flood.

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.