Channel
@G_YTO
On this record: Growth · Engagement · What this channel posts · Posts · Telegram's recommendations · Cite this entry
2,365subscribers
-3 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of 1,000–3,162.
| Telegram ID | -1001939628929 |
|---|---|
| Type | Channel |
| Username | @G_YTO |
| Created | Between 1 April 2023 and 31 October 2023— estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 13 August 2026 |
| Measurements held | 2 |
| Confirmed unchanged | 1 time, most recently 13 August 2026 |
| On Telegram | t.me/G_YTO |
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 13 Aug 2026, 02:34 | 2,365 | -3 |
| 12 Aug 2026, 16:03 | 2,368 | first reading |
18 posts held, back to 29 May 2026 — 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 pageof Telegram’s post history, 20 posts per page.
ERR is average views per post over the last 30 days divided by subscribers, the definition TGStat uses, so this figure is comparable with the one you will see elsewhere. It falls structurally as a channel grows: a high ERR on a small channel and a low one on a large channel describe reach mathematics, not quality. We publish the figure and the sample it came from and pass no verdict on it.
ER is defined industry-wide as (forwards + reactions + comments) ÷ views— note the denominator is views, not subscribers. Telegram’s public web preview carries views and reactions but not forward or comment counts, so the reaction rate above is the reactions term only and is therefore a floor: the true ER for this channel is higher by an amount we have not measured and will not estimate.
| Window | Rolling 30 days · latest post in window 22 July 2026 |
|---|---|
| Posts held | 18 (29 May 2026 – 22 July 2026) |
| Views total | 154 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 12 Aug 2026, 16:03 UTC |
Views are a single reading per post, taken at the time above. A post published in the last day or two is still accumulating views, which pulls the 30-day average down slightly. That is a property of the standard definition rather than a fault in it, so we keep the definition rather than “correcting” the number into something nobody can reproduce.
Precision. Telegram publishes view counts on its public widget in short form — 8.12K, 3.7M — so any reading at or above 1,000 reaches us rounded to three significant figures, and only counts below 1,000 are exact. Averages and rates derived from them are shown to the same precision rather than to the unit: a figure like 3,701,250 would assert digits nobody measured.
Reaction counts are published per emoji and rounded the same way, so a total below 1,000 is exact and a larger one is a sum that may carry a rounded component from each emoji above 1,000. Because it is a sum, it does not look rounded — read a large reaction total as three significant figures per contributing emoji rather than as the figure it prints.
Measured directly from 3 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.
الف مبروك للناجحين والي اجو يبشروني بنجاحهم كلش فخوره بيكم وفرحانة بيكم حيل ويارب النجاح الباهر بباقي المراحل وتوفيق الله الكم بهاي الخطوه الجديدة اما الي طلعوا بدور ثاني عادي مو مشكله بالدور الاول غلطتوا هل مره تعلموا من اغلاطكم بالدور الثاني وبالتوفيق يارب واقروا زين اريد درجات حلوة 🩶 اما الي راح يعيد السنة ادري الموضوع يقهر حيل بس الحلم يستاهل نتعب عليه اقروا واتعبوا وطلعوا ثمرات تعبكم بنحاجات ودرجات قوية وكلنا عد…
تهون وداعتَك .
شلونك بالتراب شلون كَاضيها هيج بصُورتك ضليت احاجيها المفروض الوَرد يندفن بالبُستان شجابك للكُبور شَعرفك بيها .
استاهل الحُب اني بَس ياهو اليستاهلني ؟
حزن گلبي عطر گهرب ولا يگضِي
-
-
من شفت الرّسائل صايرَات ثگال وتبات الرسالة وعود يقروها گلت ياگلبي ايس خايب نمليت ماادم الرسائل مَا يفتحوها
مستعد لو رَدّيت من الجَاهلية ذنوب العرب كلهن علية
الوَحيد الما عرَفت شلون أعبرَك !
File, posted without a caption
Photo, posted without a caption
Showing the 12 most recent of 18 posts we hold for @G_YTO. 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.
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.
This channel appears in 1 seed channel's Telegram-generated recommendation list in total. Each is Telegram’s list for THAT channel, not this one — see how this is measured.
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 August 2026 — this entry's latest reading, not the date you are reading this.
“مخبأ” (@G_YTO), 2,365 subscribers as measured 13 August 2026. Telegram Register, tgregister.com/channel/G_YTO.
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.