дорогие союзники, кф закрывается, и все союзы разрываются. рады были сотрудничеству. #𝗥𝗣_𝗗𝗘𝗦𝗧𝗜𝗡𝗬𝗠𝗜𝗡𝗧
Signed ㅤ
Channel
@destinymint
On this record: Growth · Engagement · Posts · Citations · Handles named that no longer answer · Cite this entry
2subscribers
+0 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001554367356 |
|---|---|
| Type | Channel |
| Username | @destinymint |
| Created | Between 1 August 2021 and 25 June 2022— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 16 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 16 August 2026 |
| On Telegram | t.me/destinymint |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 08:37 | 2 | no change |
| 15 Aug 2026, 11:46 | 2 | first reading |
20 posts held, back to 25 June 2022 — 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 29 June 2022. An engagement rate over an empty window would be a number about nothing.
дорогие союзники, кф закрывается, и все союзы разрываются. рады были сотрудничеству. #𝗥𝗣_𝗗𝗘𝗦𝗧𝗜𝗡𝗬𝗠𝗜𝗡𝗧
Signed ㅤ
дорогие союзники, я (@fjfjdjdjhs) ухожу в рест, и рп от меня не будет 2 недели, прошу отнестись с понимаем. те, кто захотят разорвать союз, напишите, пожалуйста в лс. #𝗥𝗣_𝗗𝗘𝗦𝗧𝗜𝗡𝗬𝗠𝗜𝗡𝗧
Signed ㅤ
конец рп от сэмушки #𝗥𝗣_𝗗𝗘𝗦𝗧𝗜𝗡𝗬𝗠𝗜𝗡𝗧
Signed ㅤ
репосты будут 26 числа после обеда по мск, так как у админа по союзам выпускной сегодня. #clowns
Signed ㅤ
Хештег для рп: #𝐒𝐎𝐌𝐌𝐄𝐋_repost
Signed ㅤ
здравствуйте, я беру рест на неделю, извините. @i_dillie_l #ᴡɪʟsᴏɴʀᴇᴘᴏsᴛ
Signed ㅤ
союзники я не умер.! #𝗜𝗡𝗙𝗡𝗧𝗬ʳᵉᵖᵒˢᵗ
Signed ㅤ
Извините дорогие союзники что вчера не было рп, в понедельник всё сделаю, мне было плохо вчера. А сейчас суббота и воскресенье выходной. #hellofаthrill_rp
Signed ㅤ
здравствуйте, дорогие союзники, я сегодня не могу провести рп по личным причинам. завтра проведу рп за два дня, спасибо за понимание. #𝗿𝗮𝗶𝗻𝘀ᶠᵃᵐ
Signed ㅤ
принимаю союзы 0+. @kkk_demian. #FM_EMDERSON
Signed ㅤ
всё-таки я не буду выкладывать союз лист.как я и раньше говорил,мне не удобно с ним работать.так же мой админ по союзам больше неделю назад по некоторым причинам ушёл.все его союзы соответственно перешли ко мне.надеюсь вопросов у вас больше не будет. #FM_EMDERSON
Signed ㅤ
извиняюсь за свою неактивность, думал сделаю все рп в выходные, но опять переношу все на понедельник. рп за все дни буду в понедельник. прошу понял и простить, чмокаю всех #rêvasserp
Signed ㅤ
Showing the 12 most recent of 20 posts we hold for @destinymint. 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.
Republishes
Channels on the register whose posts this channel has forwarded.
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 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.
@destinymint named 20 handles that resolve to nothing today. That is a fact about the reference, not necessarily a fact about the handle’s history — see the two groups below.
Most of these may never have existed as a live channel at all.A handle a channel names can be a typo, an aspirational name nobody registered, or a channel that was already gone before this one ever mentioned it. Unless a row below is marked evidenced, all we know is that it references a handle that is not a live channel today — not that anything “died”. How this is measured.
References a handle that is not a live channel — we have no record it ever was one.
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.
“ЗАКРЫТО.” (@destinymint), 2 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/destinymint.
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.