https://t.me/stxxtay/21263

Channel
𝗏𝖾𝗅𝖺𝗂𝗋
@stxxtay
On this record: Topic · Previous handles · Growth · Engagement · What this channel posts · Posts · Citations · Cite this entry
159subscribers
+96 since we began measuring on 12 August 2026
Risers and fallers across the register · movement among entries of Under 1,000.
Register entry
| Telegram ID | -1003359674368 |
|---|---|
| Type | Channel |
| Username | @stxxtay |
| Created | Between 1 November 2025 and 31 March 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated. |
| First recorded | 12 August 2026 |
| Last confirmed live | 16 November 2026 |
| Measurements held | 11 |
| On Telegram | t.me/stxxtay |
Topic
Other / unclassifiable — a classification, not a measurement. An on-box language model (Qwen3.6-35B-A3B, prompt version 1) read this channel’s own recent posts on 13 October 2026 and assigned it the closest of 31 fixed categories, at 70% 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.
Previous handles
@stxxtay was previously reachable at these 2 handles, before switching to its current one. This says nothing about who or what answers at the old handle today — only that this channel no longer does.
held 10 October 2026 – 10 October 2026
held 12 August 2026 – 12 August 2026
Growth
| Measured (UTC) | Subscribers | Change |
|---|---|---|
| 16 Nov 2026, 02:22 | 159 | no change |
| 16 Nov 2026, 01:48 | 159 | -18 |
| 13 Oct 2026, 21:06 | 177 | +4 |
| 10 Oct 2026, 14:22 | 173 | no change |
| 10 Oct 2026, 13:47 | 173 | +90 |
| 10 Sept 2026, 19:16 | 83 | -1 |
| 2 Sept 2026, 10:45 | 84 | -10 |
| 26 Aug 2026, 09:23 | 94 | +25 |
| 20 Aug 2026, 00:42 | 69 | +6 |
| 12 Aug 2026, 02:15 | 63 | no change |
| 12 Aug 2026, 02:02 | 63 | first reading |
Engagement
45 posts held, back to 11 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 3 pages of Telegram’s post history, 20 posts per page.
- ERR · 30 days
- 7.86%
- avg views ÷ 159 subscribers
- Avg views / post
- 12.5
- 20 posts measured
- Reaction rate
- —
- this channel exposes no reaction counts
- Posts in window
- 20
- of 45 held
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 15 November 2026 |
|---|---|
| Posts held | 45 (11 August 2026 – 15 November 2026) |
| Views total | 250 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 16 Nov 2026, 02:22 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.
What this channel posts
- Photos
- 89
- Videos
- 1
- Links
- 18
Lifetime counters from Telegram’s own channel header, read 16 November 2026 — not the date at the top of this page, which is when the subscriber count was last read. Below Telegram’s rounding threshold, so these counts are exact.
Recent posts
Telegram’s own ‘edited’ marker: 0 of 20 posts held from the last 30 days (0%) carried it when this register last read them. The marker says a post was changed after publishing, not what it said before — this register holds the earlier wording only where an edit fell between two of its own reads (see the edit ledger and how it is measured).
چیشده؟
Signed # 𝖫𝖺𝗌𝗄︎𝖺𝗋
((: ناز
👀 کسایی که با سوگند مشکل داشتن رابطه بین سوگند و پارتنرش که دختر بوده رو لو دادن به مدیرشون ، مدیر با سوگند حرف میزنه و سوگند اونجا التماس میکنه که به پدرش چیزی نگن ، ولی مدیر مستقیما زنگ میزنه پدرش و کل قضیه رو میگه ؛ قبل از این ، مدیر میدونسته که پدر سوگند چه آدمیه !! 👀 به نقل از همکلاسی های سوگند ، چندین بار با حالت آشفته و صورت کبود اومده مدرسه و بقیه میدونستن مشکل خانوادگی داره . 👀 و ظاهراً سه روز دیگه تولد …
👀 به نقل از همکلاسی سوگند ، دو تا خانوم دم در مدرسه اومدن جلوی پدرش رو بگیرن اونا رو انداخته زمین و داد زده به شما چه مربوطه و سوار ماشین شدن سوگند رو ساعت هشت و چهل و پنج دقیقه صبح از مدرسه میبره خونه و مثل اینکه تو خونه هم باهم دعوا میکنن و ساعت نه صبح شنبه بیست و سه ابان سوگند رو از پنجره طبقه پنجم ساختمان به پایین پرت میکنه و سوگند فوت میکنه .. و حتی بعد از مرگش گفته من به جنازه کثیفش دست نمیزنم .
Sticker, posted without a caption
Signed # 𝖫𝖺𝗌𝗄︎𝖺𝗋
در رابطه با سوگند صیادی برید تیک تاک این پست : https://www.tiktok.com/t/ZPLKjghsc/ رو شر کنید و کپی لینک کنید تا دیده بشه، همین پیام هم شر کنید پست و دیده بشه
نقل یکی از آشناهای سوگند صیادی: ما یهو دخترو از قبلت میشناختیم به شدت دختر خوبی بود از سال هشتم که راهنمایی بودیم یه زمزمه هایی میشنیدیم که این پدرش مشکل داره روانیه و و و از همون سال هشتم نهم بود با یکی از بچه ها مدرسمون یهو صمیمی شد بعضیا میگن باهم بودن بعضیا هم میگن نبودن اما ارتباطشون اوکی بود صمیمی به نظر میرسیدن تو راهنمایی مسئله ای پیش نیومد از اوایل مهر امسال سر این قضیه سوگندو سه چهار بار بردن دفتر و اذیت…
Sticker, posted without a caption
اون قدری بعد این خبر عصبی شدم که نمیدونم الان حالم و چجوری توضیح بدم.
Sticker, posted without a caption
حق
Showing the 12 most recent of 45 posts we hold for @stxxtay. 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
Republished by
Channels on the register that have forwarded this channel's posts into their own feed.
Republishes
Channels on the register whose posts this channel has forwarded.
@dw3litttt · 2394 postsدشـت بــابــونــہ
@wethgedon · 2063 postshervoice͏ ͏#feminism
@feministie · 1,2822 posts 𝖱𝖾𝗀ı𝗇𝖺𝖾 ' خلوتباملکهها
@ktaejk · 1272 postsشما در تئاتر هستید.
@JaaeKeHasti · 24,1051 post عـطـرِ کـاغـذِ کـهنـه ﹙فولدر﹚
@Milancoffe · 7271 post𝖡𝖾᥆𝗆 𝖼𝗅𝗎𝖻 ໒꒱‧
@beomclub01 · 1,4431 postcastle
@castleofwomen · 7,6991 postcannibal : erotic religious.
@clovesngun · 2751 postHerstory فمیـنیـسم
@itherstory · 14,6291 post 𝖺𝗇𝗀𝖾𝗅'𝗌 𝗁𝗈𝗎𝗌𝖾 رندومپك
@luvkissangel · 7651 post 𝖶𝗈𝗅𝖿𝗂𝖾
@stayswolfie · 361 post
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
Named by 1 registered channel — 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.
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.
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 16 November 2026 — this entry's latest reading, not the date you are reading this.
“ 𝗏𝖾𝗅𝖺𝗂𝗋” (@stxxtay), 159 subscribers as measured 16 November 2026. Telegram Register, tgregister.com/channel/stxxtay.
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.