Telegram RegisterThe public register of Telegram
Telegram profile photo for -نامه‌هایِ اتوبوسی-

Channel

-نامه‌هایِ اتوبوسی-

@nameotbosy

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

260subscribers

+141 since we began measuring on 6 August 2026

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

Register entry

Telegram ID-1004463924198
TypeChannel
Username@nameotbosy
CreatedBetween 1 June 2026 and 31 July 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded9 August 2026
Last confirmed live13 September 2026
Measurements held8
Confirmed unchanged1 time, most recently 13 September 2026
On Telegramt.me/nameotbosy

Growth

1192892046 August 2026 — 119 subscribers7 August 2026 — 129 subscribers9 August 2026 — 129 subscribers15 August 2026 — 160 subscribers22 August 2026 — 182 subscribers28 August 2026 — 200 subscribers5 September 2026 — 289 subscribers13 September 2026 — 260 subscribers2606 August 202613 September 2026
8 measurements spanning 38 days, net +141. 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 94–315 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
13 Sept 2026, 11:55260-29
5 Sept 2026, 11:01289+89
28 Aug 2026, 20:37200+18
22 Aug 2026, 15:29182+22
15 Aug 2026, 16:17160+31
9 Aug 2026, 01:16129no change
7 Aug 2026, 11:15129+10
6 Aug 2026, 18:02119first reading

Engagement

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

What this channel posts

Video runtime
21s
Average length
21s

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.

Reaction mix

340 reactions across 18 posts, in 5 distinct kinds. The most used accounts for 62.6% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
🍓21362.6%
💘4713.8%
💔3710.9%
👍308.82%
😭133.82%

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 18 of the 18 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 340 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 18 most recent posts we hold, published 31 July 2026 to 7 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

7 Aug 2026, 12:30 UTC86 views21 reactionsread 9 August 2026

-ترش رویی هم بکن شیرین عسل بانوی من گاه گاهی قاطی فالوده لیمو لازم است! .

🍓15😭4💘2

6 Aug 2026, 11:52 UTC82 views18 reactionsread 9 August 2026

-نیاز دارم محتویاتِ‌مغزم رو به اشتراک بزارم

💔15🍓3

5 Aug 2026, 20:36 UTC90 views21 reactionsread 9 August 2026

بسیار برای تو نوشتم غم خود را بسیار مرا نامه ، ولی نامه‌بری نیست*

🍓16💘3💔2

5 Aug 2026, 20:35 UTC77 views20 reactionsread 9 August 2026
Photo

Photo, posted without a caption

🍓15💘5

5 Aug 2026, 20:21 UTC77 views13 reactionsread 9 August 2026

-روزها با سرعتی بیش از حد معمول مانند صفحات کتاب ورق می‌خورند و من هم پس از هر کدام از صفحات میفهمم که هیچ چیز نخوانده‌م دلم میگوید به عقب برگرد دوباره خاطرات را مرور کن شاید چیزی حیرت انگیز میان آن ها پیدا کنی اما مغزم این حقیقت که هیچ چیز جالبی در آن صفحات نیست را به محکمی به صورتم میکوبد و طبیعتا من مبهوت روز های گذرانده شده هستم آن ها کی آمدند و کی رفتند که من خبردار نشدم؟دارم چکار میکنم؟این روزها مال من هستند؟من

🍓10💘3

5 Aug 2026, 08:46 UTC83 views20 reactionsread 9 August 2026

-ما که دل کندیم از او دیگر چه فرقی میکند؟ با سگان زرد باشد یا شغالان سیاه*

🍓17👍3

3 Aug 2026, 08:46 UTC133 views19 reactionsread 9 August 2026

-با شجاعت عقل من ، تسلیم چشمان تو است- -آن دو گوی قهوه ای ، از عقل من دل برده اند-

🍓19

2 Aug 2026, 14:59 UTC126 views20 reactionsread 9 August 2026

-دو دفترچه‌ی موازی² . چشمانش را با بی‌حوصلگی از دفترچه گرفت و هوفی از ته دل کشید؛ اصلاً دلش نمی‌خواست اتفاقات صبح را دوباره مرور کند. دفترچه را روی میز گذاشت تا بعداً سراغش برود، اما وقتی زمانِ رسیدگی به پروژه‌ها شد، تازه فهمید ایده‌های اصلی‌اش را همان صبح داخل دفترچه یادداشت کرده بود. قرار بود امشب به آن‌ها نگاهی بیندازد.. و همان لحظه بود که «کلکسیون بدبختی‌های امروز» کامل شد. کم مانده بود گریه‌اش بگیرد؛ تنها کاری

🍓17😭2💔1

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

Mentions

Named by 3 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.

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

“-نامه‌هایِ اتوبوسی-” (@nameotbosy), 260 subscribers as measured 13 September 2026. Telegram Register, tgregister.com/channel/nameotbosy.

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.