Telegram RegisterThe public register of Telegram
Telegram profile photo for مـادرید، دروازه‌ے خورشیـد.

Channel

مـادرید، دروازه‌ے خورشیـد.

@fromleeyongbok

On this record: Topic · Growth · Engagement · What this channel posts · Posts · Citations · Telegram's recommendations · Cite this entry

594subscribers

-11 since we began measuring on 14 September 2026

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

Register entry

Telegram ID-1001418122217
TypeChannel
Username@fromleeyongbok
CreatedBetween 1 April 2019 and 31 October 2021 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded14 September 2026
Last confirmed live5 November 2026
Measurements held8
Confirmed unchanged1 time, most recently 5 November 2026
On Telegramt.me/fromleeyongbok

Topic

Personal blog — 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 28 September 2026 and assigned it the closest of 31 fixed categories, at 37% 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 the other topics.

Growth

590607598.514 September 2026 — 605 subscribers14 September 2026 — 605 subscribers28 September 2026 — 607 subscribers8 October 2026 — 601 subscribers16 October 2026 — 604 subscribers23 October 2026 — 599 subscribers30 October 2026 — 590 subscribers5 November 2026 — 594 subscribers59414 September 20265 November 2026
8 measurements spanning 53 days, net -11. 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 587–610 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
5 Nov 2026, 20:50594+4
30 Oct 2026, 06:21590-9
23 Oct 2026, 22:06599-5
16 Oct 2026, 10:00604+3
8 Oct 2026, 22:18601-6
28 Sept 2026, 09:56607+2
14 Sept 2026, 05:22605no change
14 Sept 2026, 04:47605first reading

Engagement

19 posts held, back to 28 October 2024 — 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 19 posts for this entry, the most recent from 29 October 2025. An engagement rate over an empty window would be a number about nothing.

What this channel posts

Video runtime
14s
Average length
14s

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.

Recent posts

29 Oct 2025, 19:02 UTC≈1,500 viewsread 14 September 2026

تو فرق داشتي. با همه‌ی آدم‌ها. تو نرگس بودی. نرگسِ پژمرده‌ای که می‌ترسیدم لمسش کنم، مبادا نشکنه. نرگسي که نشد گل کوچولوی قلبِ من باشه.

28 Oct 2025, 08:40 UTC≈1,370 viewsread 14 September 2026

گفتن این رو با حسی که از نوشته‌های اینجا گرفتن نوشتن، پس ترجیح می‌دم اینجا بمونه.

28 Oct 2025, 08:39 UTC≈1,340 viewsread 14 September 2026
Forwarded from @urjinus

‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ دۈ ࢪﺅ‌ح، دۈ ࢪنگ، دۈ تن در آغۈش یك ࢪویا‌ ‌ بر آینه‌ی آرام دریاچه، دو رویا می‌درخشیدند یکی سپید چون سپیده‌دم، و دیگری سیاه چون آسمان عمیق پس از باران در شب. هنگامی که آن دو در کنارهم بر تن سرد دریاچه آغاز به رقص میکردند شورِ عشق میانشان قطره به قطره‌ی آب دریاچه را بسوی آغوشی گرم راهی میکرد، آنان بی‌نیاز از واژه و تنها با نگاهی، دل‌های عاشق خود را به هم گره می‌زدند. در نگاه اول، کم‌تر کسی پ…

14 Oct 2025, 07:09 UTC≈1,260 viewsread 14 September 2026

کاش یک‌نفر یک‌جوری دوست نداشتنت رو یادم می‌داد.

11 Oct 2025, 16:14 UTC≈1,280 viewsread 14 September 2026

نرسیدن به چیزهایی که دوستشون داری دردناکه. و اگر این چیزها آدم باشن، آدم‌مورد علاقه باشن، بیشتر دردناک میشه. چون مدام از خودت می‌پرسي چرا؟ چی‌شد؟ چی‌ می‌شد اگر می‌شد؟ مگه چیکار کردم که نباید بهش برسم و این فکرها هیچ‌وقت تموم نمی‌شن.

28 Sept 2025, 22:08 UTC≈1,390 viewsread 14 September 2026

فراموش کردن احساسات یه‌چیزه، ترک کردنش یه چیز دیگه. این هم که من نمی‌خوام دوست داشتنت رو فراموش و ترک کنم یه‌چیز جدای دیگه ـست.

2 Apr 2025, 21:37 UTC≈3,270 viewsread 14 September 2026
Forwarded from @cooiceo

I told the stars about you.

15 Feb 2025, 21:58 UTC≈4,050 viewsread 14 September 2026

اگر به گذشته‌ها برمی‌گشتیم، بازهم برای نجاتم به زحل میومدی؟

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

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.

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.

Appears in Telegram’s recommendations for other channels

The reverse of the list above, and a different kind of signal. This does not require this channel to have ever been asked about directly — each row below is a channel we DID ask Telegram about, whose Telegram-generated list happened to include this one. A channel can appear here with an empty list above it, because being named by someone else’s query is independent of having been queried itself.

قبیله‌خورشیدِنیمه‌شب.
@Abani_Blue · 23,865
Telegram ranks this channel #12 of 68 here — alongside 67 others — read 16 September 2026
نیم‌فنجان‌ واژه
@harinmood · 21,776
Telegram ranks this channel #17 of 69 here — alongside 68 others — read 29 September 2026
𝐍𝐠𝐚𝐫ִֶָ ☽︎۪ ࣪
@The_Ngar · 22,654
Telegram ranks this channel #23 of 70 here — alongside 69 others — read 24 September 2026
Bonyad_Nohomiha
@bonyad_nohomihaa · 24,909
Telegram ranks this channel #37 of 55 here — alongside 54 others — read 14 September 2026

This channel appears in 4 seed channels' Telegram-generated recommendation lists in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.

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

“مـادرید، دروازه‌ے خورشیـد.” (@fromleeyongbok), 594 subscribers as measured 5 November 2026. Telegram Register, tgregister.com/channel/fromleeyongbok.

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.