Channel
@Challengetimee0_0
On this record: Topic · Growth · Engagement · What this channel posts · Reactions · Posts · Citations · Handles named that no longer answer · Cite this entry
8,632subscribers
+848 since we began measuring on 6 August 2026
Risers and fallers across the register · movement among entries of 3,162–10,000.
| Telegram ID | -1001683037268 |
|---|---|
| Type | Channel |
| Username | @Challengetimee0_0 |
| Created | Between 1 December 2021 and 30 April 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 6 August 2026 |
| Last confirmed live | 15 September 2026 |
| Measurements held | 14 |
| Confirmed unchanged | 1 time, most recently 15 September 2026 |
| On Telegram | t.me/Challengetimee0_0 |
Gaming — 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 11 September 2026 and assigned it the closest of 31 fixed categories, at 98% 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 why it has no browse page of its own yet.
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 15 Sept 2026, 13:19 | 8,632 | +116 |
| 11 Sept 2026, 11:38 | 8,516 | +82 |
| 6 Sept 2026, 18:38 | 8,434 | +105 |
| 2 Sept 2026, 09:45 | 8,329 | +65 |
| 30 Aug 2026, 08:34 | 8,264 | +67 |
| 27 Aug 2026, 13:33 | 8,197 | +34 |
| 25 Aug 2026, 00:05 | 8,163 | +89 |
| 21 Aug 2026, 04:27 | 8,074 | +64 |
| 18 Aug 2026, 12:22 | 8,010 | +25 |
| 15 Aug 2026, 19:48 | 7,985 | +68 |
| 12 Aug 2026, 12:14 | 7,917 | +57 |
| 9 Aug 2026, 21:31 | 7,860 | +76 |
| 6 Aug 2026, 21:45 | 7,784 | no change |
| 6 Aug 2026, 21:34 | 7,784 | first reading |
267 posts held, back to 6 August 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 20 pages of 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. It is computed over the 9 of 68 measured posts that carry a reaction reading, and over those same posts' views.
| Window | Rolling 30 days · latest post in window 28 August 2026 |
|---|---|
| Posts held | 267 (6 August 2026 – 28 August 2026) |
| Views total | 13,315 |
| Reactions total | 11 |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 28 Aug 2026, 18:26 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 5 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.
103 reactions across 43 posts, in 6 distinct kinds. The most used accounts for 42.7% of them.
| Reaction | Count | Share | Share, drawn |
|---|---|---|---|
| 🍓 | 44 | 42.7% | |
| 💘 | 28 | 27.2% | |
| 👾 | 13 | 12.6% | |
| 🆒 | 9 | 8.74% | |
| 👀 | 7 | 6.80% | |
| 🐳 | 2 | 1.94% |
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 46 of the 267 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 103 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.
Measured over the 267 most recent posts we hold, published 6 August 2026 to 28 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.
💭𝓕𝗋𝗐𝖽 𝗍𝗁𝗂𝗌 𝗆𝖾𝗌𝗌𝖺𝗀𝖾 𝖺𝗇𝖽 ۫ ܺ 𝗍𝖾𝗅𝗅 𝗆𝖾 𝗒𝗈𝗎𝗋 𝖿𝖺𝗏𝗈𝗋𝗂𝗍𝖾 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋 𝗇 𝖨'𝗅𝗅 ⳿ ◜𝗀𝗂𝗏𝖾 𝗒𝗈𝗎 𝖺𝗇 𝖾𝖽𝗂𝗍 𝖻𝖺𝗌𝖾𝖽 ㅤ ㅤ࣪ ㅤ 𓈒 ۫ ㅤ 𝂮◟𝗈𝗇 𝗍𝗁𝖾 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋 𝗒𝗈𝗎 𝖼𝗁𝗈𝗈𝗌𝖾 ◞ ꒰ 𝗒𝗈𝗎'𝗅𝗅 𝖿𝗂𝗇𝖽 𝗈𝗎𝗍 𝖺𝗍 𝗍𝗁𝖾 𝖾𝗇𝖽 יִ יִ ꒱𑪍 if you like join:3 — 𝗉𝗋𝗂𝗏𝖺t
این پیام رو فوروارد کنید تا بهتون بگم تو دنیای گنشین/استار ریل، چه المنت، فکشن، رریتی، کیت و پلی استایلی دارید و با کدوم یکی از کارکتر ها و چطوری باهاشون در ارتباطید و اگه اسکین میگرفتید چه شکلی بود و داستان پشتش چی بود✨️ . ݁₊ ⊹ . ݁ ⟡ ݁ . ⊹ ₊ ݁. - لطف کنید حتما بین سه تا بازی یکی رو انتخاب کنید. (میتونم براتون از zzz و reverse 1999 هم بدم اگه دوست داشتید ولی متاسفانه اونقدر روش تسلط نخواهم دا…
فروارد کنید چنل پابلیک خودتون یا هر اوسی ای که میخواید رو تردیشنال براتون میکشم 20 نفر فقط البته 5 نفر اول رو کامل رنگ و رندر میکنم 5 نفر دوم رو فقط رنگ میکنم دیگه دیتیل نمیدم بقیه هم فقط اسکچ
ֶָ֪ ׂ﹏ ֪ ⊹ ﹏ ֶָ֪ ⊹ ﹏ ׅ ⊹ ֶָ֪﹏ ֶָ֪ 𝝑୧: 𝖥𝗈𝗋𝗐𝖺𝗋𝖽 𝗍𝗁𝗂𝗌 𝗆𝖾𝗌𝗌𝖺𝗀𝖾, 𝖺𝗇𝖽 𝖨’𝗅𝗅 𝗆𝖺𝗄𝖾 𝖺 𝗉𝗂𝖼𝗍𝗎𝗋𝖾 𝗅𝗂𝗄𝖾 𝗍𝗁𝗂𝗌 𝖻𝖺𝗌𝖾𝖽 𝗈𝗇 𝗒𝗈𝗎𝗋 𝗏𝗂𝖻𝖾. ✶ ֶָ֪ ׂ﹏ ֪ ⊹ ﹏ ֶָ֪ ⊹ ﹏ ׅ ⊹ ֶָ֪﹏ ֶָ֪ Limit: 15 Be sure to join pls 😭
ㅤㅤㅤㅤㅤℱ𝓸𝓻𝔀𝓪𝓻𝓭 𝗍𝗁𝗂𝗌 𝗆𝖾𝗌𝗌𝖺𝗀𝖾 𝖺𝗇𝖽 𝓘𝓸𝓲𝓷 𝗂𝗇 𝗍𝗁𝖾 𝖼𝗁𝖺𝗇𝗇𝖾𝗅. 𝗍𝖾𝗅𝗅 𝗆𝖾 𝗒𝗈𝗎𝗋 𝑓𝑎𝑣 𝖼𝗈𝗅𝗈𝗋. 𝖻𝖺𝗌𝖾𝖽 𝗈𝗇 𝗒𝗈𝗎𝗋 𝖼𝗁𝖺𝗇𝗇𝖾𝗅'𝗌 𝗏𝗂𝖻𝖾 𝖺𝗇𝖽 𝗒𝗈𝗎𝗋 𝖿𝖺𝗏, 𝖨'𝗅𝗅 𝗍𝖾𝗅𝗅 𝗐𝗁𝖺𝗍 𝗒𝗈𝗎𝗋 𝑅𝑜𝑙𝑒 𝗂𝗇 𝖺 𝐺𝑟𝑜𝑢𝑝 & 𝗐𝗂𝗍𝖼𝗁 𝖺𝗇𝗂𝗆𝖾 𝗈𝗋 𝗀𝖺𝖼𝗁𝖺 𝗀𝖺𝗆𝖾 𝖼𝗁𝖺𝗋𝖺𝖼𝗍𝖾𝗋 𝗒𝗈𝗎 𝗅𝗈𝗈𝗄 𝗅𝗂𝗄𝖾. ㅤㅤㅤㅤㅤㅤㅤㅤℒ𝓲𝓶𝓲𝓽: 𝗂𝖽𝗄 ㅤㅤㅤㅤㅤ𝓘 𝓪𝓷𝓼𝔀𝓮𝓻 𝔂𝓸𝓾 ℒ𝓲𝓴𝓮 𝒯𝓱𝓲𝓼
Forward this and I'll give you a rpg horror game 🪷
!¡ Forward this message and I'll give you a rock/metal song from my playlist based on your vibe. Private?come here.
این پیام رو فور کنید تو چنلاتون تا من یه سری اتفاقاتی که تا ماه آینده قرار هست براتون بیوفته رو بهتون بگم🕯 حتما جوین باشید اسم و سنتون هم بگید🍓 ❤️پرایوت ها لینک بدید❤️
•✟• Challenge •✟• این آرتی که ریپلای کردم و این پیامو تو چنلتون فور کنین و یکی از کاراتونو مشخص کنید تا من فور کنم چنلم ⭐️🍰 چنل هنری باشه لیمیت : نمیدونم خط میزنم @Challengetimee0_0 ⋆
˖ ࣪ ֪ ࣪ . 🤍 این تکست رو توي چنلتون فوروارد کنید، از زیباییتون ریپلای کنید تا . . من با توجة به وایبتون، خوراکي و کیك تولد بدم و حیات هم بهتون یه غذای یامي میده🐰 مطمئنشید کة توي هردو چنل جوین باشید اگر بعد از چنلج لف بدید بن میشید
ᯓᝰ 𝚏𝙾𝚁𝚆𝙰𝚁𝙳 𝚃𝙷𝙸𝚂 𝙼𝙴𝚂𝚂𝙰𝙶𝙴 ‧ ִֶָ ⊹ And I'll send you a Japanese poem or quote. ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː࿙᷍࿚ː Privates : @IamYourHopeBot 𖹭 Limit : Till I cross out.
🍓1
Forward this message and I'll give you a TV show/movie based on ur vibe. ( I'll tell u which character suits u based on ur vibe )
Showing the 12 most recent of 267 posts we hold for @Challengetimee0_0. 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.
Republishes 174 registered channels. The 48 listed are the ones this channel has forwarded most; the rest are counted here but not each listed.
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 120 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. The 23 listed below are the most frequent namers; the rest are counted above but not each listed.
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.
@Challengetimee0_0 named 7 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.
We ourselves saw each of these resolve to a real page at some point before it went vacant — a genuine, evidenced change, not an inference from absence.
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 15 September 2026 — this entry's latest reading, not the date you are reading this.
“𖥻 𝖼𝗁𝖺𝗅𝗅𝖾𝗇𝗀𝖾𝗌 ⋆” (@Challengetimee0_0), 8,632 subscribers as measured 15 September 2026. Telegram Register, tgregister.com/channel/Challengetimee0_0.
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.