Channel
@T_O_O_F_A_N_T_K_M_5_5_1_4
On this record: Growth · Engagement · What this channel posts · Posts · Citations · Handles named that no longer answer · Cite this entry
1subscribers
+0 since we began measuring on 15 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
| Telegram ID | -1001354234817 |
|---|---|
| Type | Channel |
| Username | @T_O_O_F_A_N_T_K_M_5_5_1_4 |
| Created | Between 1 March 2018 and 19 February 2019 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 15 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 5 times, most recently 17 September 2026 |
| On Telegram | t.me/T_O_O_F_A_N_T_K_M_5_5_1_4 |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Aug 2026, 09:04 | 1 | no change |
| 15 Aug 2026, 07:32 | 1 | first reading |
8 posts held, back to 19 February 2019 — 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 8 posts for this entry, the most recent from 22 February 2019. An engagement rate over an empty window would be a number about nothing.
Measured directly from 1 video 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.
اینم بلاکی بیناموسس ها تبر زن ها همه شون بلاک کرده نصب شون ج نمیدا از ترسسسس #کوروش_تک_پسر_هراتم نبینم تو فکر اتک باشین باخت همه رو گرفتم هم زمانی ۶ تا ناموسس گرفتم🤣😳😂😂😂 پرونده شون بسته شد باعی🤒
ناموسن هرچی گفته واقعیته😓💔اهنگشو هرکسی داره بفرسته 😓تبرو همیشه از نزدیکترین دوستت یا عشقت میخوری #کوروش_تک_پسر_هراتم😔😔😔
@BudyBuilder_Mah @Erfan_Kaboos_12 @kos_nanam_shod_khkhkhkh @kiarash_123کیر ب نصلتون😂😕گدای سرکوچه قیافها رو😂مادر فریب خوردها از تخم عربین دیگه کیر تو نصل تون بشه قصم میخورم یکی تون از اب پدرتو نی
@BudyBuilder_Mah @Erfan_Kaboos_12 @kos_nanam_shod_khkhkhkh @kiarash_123 @BudyBuilder_Mah خب خب کوروش تک پسر هراتم تک تاپیر تل بکن نصل ایرانی فردا ناموسسسس این تبر زنها رو میگام ناموسس تک تک شون رو کیرم سوار میکنم https://t.me/T_O_O_F_A_N_T_K_5_5_1_1
خب خب هر اخبار بنر داشتی پی بزار تا بزنم ۱۵ تا چنل اتحادی https://t.me/T_O_O_F_A_N_T_K_5_5_1_1 ایدیم🖕❤️❤️❤️
Voice message, posted without a caption
رامین روانی پی باش اگه تکستمو دیدی,سریع بیا خاص👇🏻 @Malake_Yakhiiiiiiiiii
Posted without readable text
Showing the 8 most recent of 8 posts we hold for @T_O_O_F_A_N_T_K_M_5_5_1_4. 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 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.
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.
@T_O_O_F_A_N_T_K_M_5_5_1_4 named 4 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.
“افم بای کوروشم” (@T_O_O_F_A_N_T_K_M_5_5_1_4), 1 subscribers as measured 16 August 2026. Telegram Register, tgregister.com/channel/T_O_O_F_A_N_T_K_M_5_5_1_4.
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.