Telegram RegisterThe public register of Telegram
Telegram profile photo for destan family

Channel

destan family

@fmsultan

On this record: Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry

1subscribers

+0 since we began measuring on 27 August 2026

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

Register entry

Telegram ID-1001636493866
TypeChannel
Username@fmsultan
CreatedBetween 1 December 2021 and 7 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded27 August 2026
Last confirmed live28 August 2026
Measurements held2
Confirmed unchanged1 time, most recently 28 August 2026
On Telegramt.me/fmsultan

Growth

127 Aug 2026, 23:46 — 1 subscribers28 Aug 2026, 12:25 — 1 subscribers27 Aug 2026, 23:4628 Aug 2026, 12:25
2 measurements taken within a single day. 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”.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
28 Aug 2026, 12:251no change
27 Aug 2026, 23:461first reading

Engagement

14 posts held, back to 7 April 2023the 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 14 posts for this entry, the most recent from 10 April 2023. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
2m 37s
Average length
20s

Measured directly from 8 videos with a duration reading, out of the posts we hold for this channel — not this channel’s whole posting history, only the sample this register has actually read. An exact reading to the second, taken from the post itself rather than from Telegram’s own rounded chrome, so it carries no mark.

Recent posts

10 Apr 2023, 09:13 UTC328 viewsread 27 August 2026

❗️здравствуйте дорогие союзники я очень занята поэтому рп будут по 3 раза в неделю прошу не разрывать союз, надеюсь вы поймёте. ❗️ #rpdestan

10 Apr 2023, 09:07 UTC164 viewsread 27 August 2026
Forwarded from @burkutskieVideo

cr: хина. #бүркүтские

10 Apr 2023, 09:07 UTC160 viewsread 27 August 2026
Forwarded from @burkutskieVideo

cr: айсо. #бүркүтские

10 Apr 2023, 09:07 UTC102 viewsread 27 August 2026
Forwarded from @burkutskieVideo

cr: хина. #бүркүтские

10 Apr 2023, 09:07 UTC85 viewsread 27 August 2026
Forwarded from @burkutskieVideo

cr: хина. #бүркүтские

10 Apr 2023, 09:07 UTC61 viewsread 27 August 2026
Forwarded from @burkutskieVideo

cr: хина. #бүркүтские

10 Apr 2023, 09:06 UTC58 viewsread 27 August 2026
Forwarded from @daekuww

Проверка союзников ( @xiaoluev ) на активность Пишем канал - следящий - доп пдп (если они есть) Пример: @PeachDeliiight - @ruhezis - @qqqhhs Время до 16.04.23 Те кто не отпишуться хз пока что с ними будет .Но будем проводить муторный разговор со следящим канала который не отпишиться и если причина тупая то - РАЗРЫВ #Peach_delightMEGA

10 Apr 2023, 09:05 UTC53 viewsread 27 August 2026

скора проверяю всех следящих и доп. многие доп админы даже не подписались, чеза беспредел? #METSUYOPOST #metsuyo мега/

10 Apr 2023, 09:04 UTC54 viewsread 27 August 2026
Forwarded from @hkmfm

прошу прощения союзники мои, что не был активным несколько дней подряд, если кто разорвал союз, можете мне (@AM47ONG) в лс написать (?) союзы мне +50 (@AM47ONG) #dsvRP | МЕГА РП |

7 Apr 2023, 16:59 UTC90 viewsread 27 August 2026

здравствуйте дорогие союзники, я новый админ по союзу, все союзы @jenxsua переходят ко мне @crshxzsho , по всем вопросам обращайтесь ко мне. #rpdestan [не рп]

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

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.

Mentions

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.

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

“destan family” (@fmsultan), 1 subscribers as measured 28 August 2026. Telegram Register, tgregister.com/channel/fmsultan.

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.