Channel
@sinoxapi
On this record: Topic · Growth · Engagement · Posts · Posts edited after publishing · Citations · Cite this entry
11,330subscribers
+415 since we began measuring on 27 August 2026
Risers and fallers across the register · movement among entries of 10,000–31,623.
| Telegram ID | -1003538888219 |
|---|---|
| Type | Channel |
| Username | @sinoxapi |
| Created | 5 August 2026 — measured — dated from the channel’s first post |
| First recorded | 27 August 2026 |
| Last confirmed live | 17 September 2026 |
| Measurements held | 12 |
| Confirmed unchanged | 1 time, most recently 17 September 2026 |
| On Telegram | t.me/sinoxapi |
Technology — 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 61% 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 |
|---|---|---|
| 17 Sept 2026, 05:21 | 11,330 | +182 |
| 15 Sept 2026, 05:58 | 11,148 | -24 |
| 13 Sept 2026, 15:21 | 11,172 | +207 |
| 11 Sept 2026, 22:14 | 10,965 | -61 |
| 3 Sept 2026, 22:38 | 11,026 | +1 |
| 2 Sept 2026, 13:28 | 11,025 | +2 |
| 31 Aug 2026, 15:06 | 11,023 | +2 |
| 30 Aug 2026, 13:36 | 11,021 | +60 |
| 29 Aug 2026, 10:32 | 10,961 | +16 |
| 28 Aug 2026, 12:16 | 10,945 | +30 |
| 27 Aug 2026, 20:15 | 10,915 | no change |
| 27 Aug 2026, 20:00 | 10,915 | first reading |
27 posts held, back to 5 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 6 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.
| Window | Rolling 30 days · latest post in window 2 September 2026 |
|---|---|
| Posts held | 27 (5 August 2026 – 2 September 2026) |
| Views total | 23,710 |
| Reactions total | — |
| Forwards / comments | not exposed by the public surface — not measured, not estimated |
| Readings taken | 3 Sept 2026, 02:15 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.
استفاده از کلید هدیه ۱۰ میلیون توکنی در محیط سایت فراهم شد🥳 از این به بعد میتونین بعد از اسکن کارت هدیه خودتون و ورود به بخش باشگاه مشتریان با زدن دکمه تست همه مدل ها در محیط پلی گراند همانجا از هر مدلی که دلتون خواست استفاده کنین🎧
درگاه زرین پال به صورت موقت با سابدامین در دسترس قرار گرفت بعد از تایید نهایی دامین اصلی درگاه زرین پال به صورت کامل در دسترس قرار خواهد گرفت و به عنوان یکی از روش های پرداخت به صورت دائمی روی سایت قرار خواهد گرفت🥰
دیگه فقط متن نیست😇 تصویر و ویدیو هم میسازیم😎 به زودی مدل های عکس و ویدیو به sinoxapi اضافه میشن😉
تو سالن ۴۰A پیدامون کنین🥰
فقط ۲ روز مونده تا الکامپ😉
مشکل حل شده و میتونین کامل بدون هیچ خطا و فیلترشکنی و تنها از ip ایران مستقیم کانکت بشین
آدرس دامین سایت از جانب ۲ isp فیلتر شده پیگیر موضوع هستیم و سعی بر برطرف کردنش داریم یک آدرس پشتیبان بدون فیلتر به زودی توی پنل کاربری کاربران قرار خواهد گرفت.🥰
به لیست مدل های رکوست بیس هم اضافه شد👌
مدل GLM 5.3 Flash به لیست مدل های توکن بیس ما اضافه شد😉
تو sinoxapi چه ۱۰۰ توکن باشه پرامپتت چه ۱۰۰ هزار توکن هزینش یکیه🥰 https://sinoxapi.com
به لیست مدل های رکوست بیس هم اضافه شد😉
مدل GLM 5.3 به لیست مدل های توکن بیس ما اضافه شد😎
Showing the 12 most recent of 27 posts we hold for @sinoxapi. 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.
@sinoxapi edited 1 post after it first published — the same permalink now carries different wording than the one this register originally read, caught because our own crawl held a copy of the earlier text.
An edit is not deception. Typo fixes, price updates and corrections look exactly like this too — this register can tell you the wording changed and when, not why. How this is measured.
Named by 7 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.
Named by
Channels on the register whose posts name this channel's handle.
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.
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 17 September 2026 — this entry's latest reading, not the date you are reading this.
“sinox api” (@sinoxapi), 11,330 subscribers as measured 17 September 2026. Telegram Register, tgregister.com/channel/sinoxapi.
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.