Channel
@yaoicity
On this record: Topic · Growth · Engagement · Posts · Cite this entry
3,464subscribers
-240 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001444304307 |
|---|---|
| Type | Channel |
| Username | @yaoicity |
| Created | 11 January 2019 — measured — dated from the channel’s first post |
| First recorded | 6 August 2026 |
| Last confirmed live | 3 November 2026 |
| Measurements held | 25 |
| Confirmed unchanged | 1 time, most recently 3 November 2026 |
| On Telegram | t.me/yaoicity |
Literature — 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 14 September 2026 and assigned it the closest of 31 fixed categories, at 94% 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.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 3 Nov 2026, 10:06 | 3,464 | -7 |
| 31 Oct 2026, 05:56 | 3,471 | -3 |
| 28 Oct 2026, 05:09 | 3,474 | -6 |
| 25 Oct 2026, 05:27 | 3,480 | -7 |
| 22 Oct 2026, 15:15 | 3,487 | -7 |
| 19 Oct 2026, 01:28 | 3,494 | -7 |
| 15 Oct 2026, 23:08 | 3,501 | -4 |
| 13 Oct 2026, 00:26 | 3,505 | -13 |
| 6 Oct 2026, 17:58 | 3,518 | -20 |
| 29 Sept 2026, 15:21 | 3,538 | -27 |
| 19 Sept 2026, 04:21 | 3,565 | -18 |
| 14 Sept 2026, 11:41 | 3,583 | -9 |
| 11 Sept 2026, 00:40 | 3,592 | -8 |
| 6 Sept 2026, 04:16 | 3,600 | -14 |
| 1 Sept 2026, 18:14 | 3,614 | -15 |
| 29 Aug 2026, 14:25 | 3,629 | -14 |
| 27 Aug 2026, 00:08 | 3,643 | -12 |
| 23 Aug 2026, 21:14 | 3,655 | -9 |
| 20 Aug 2026, 02:08 | 3,664 | -12 |
| 16 Aug 2026, 16:19 | 3,676 | first reading |
3 posts held, back to 11 January 2019 — the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 3 pages 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 3 posts for this entry, the most recent from 30 May 2023. An engagement rate over an empty window would be a number about nothing.
عزیزان یسریاتون چندین بار درخواست عضویت میدید ولی رد میشه وقتی میخوایم ادتون کنیم، اد نمیشید احتمالا یا تلتون باگ داره یا تعداد چنل‌ها و گروه‌هاتون زیاده از چند تا از چنلایی که نمیخواید لفت بدید یا اگه مطمئنید تعدادشون زیاد نیست تلتون رو عوض کنید یا از اکانت دیگه ای استفاده کنید
به کهکشان یائویی خوش اومدین🫧🥀 ارائه دهنده بهترین کیفیت ترجمه و ادیت وبتون‌ها و رمان‌های یائویی در متنوع ترین ژانرها🫧🥀 چنل اصلی 🫧🥀 چنل دوم (معرفی وبتون‌ها) 🫧🥀 چنل انیمه (یائویی) 🫧🥀 گپ اصلی 🫧🥀
Channel created
Showing the 3 most recent of 3 posts we hold for @yaoicity. 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.
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 3 November 2026 — this entry's latest reading, not the date you are reading this.
“Yaoi City 💛 محافظ” (@yaoicity), 3,464 subscribers as measured 3 November 2026. Telegram Register, tgregister.com/channel/yaoicity.
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.