Telegram RegisterThe public register of Telegram
Telegram profile photo for Sourcer

Channel

Sourcer

@Sourcer_ch

On this record: Growth · Engagement · Posts · Citations · Cite this entry

479subscribers

+100 since we began measuring on 2 September 2026

Risers and fallers across the register · movement among entries of Under 1,000.

Register entry

Telegram ID-1003912579069
TypeChannel
Username@Sourcer_ch
CreatedBetween 1 April 2026 and 6 August 2026 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded2 September 2026
Last confirmed live11 September 2026
Measurements held3
Confirmed unchanged1 time, most recently 11 September 2026
On Telegramt.me/Sourcer_ch

Growth

3794794292 September 2026 — 379 subscribers3 September 2026 — 412 subscribers11 September 2026 — 479 subscribers2 September 202611 September 2026
3 measurements spanning 9 days, net +100. Dots are measurements; the straight line between them is drawn to join them, not to claim we know the path taken in between — snapshots are recorded only when a count changes, so gaps mean “no change observed”, never “interpolated”. The vertical axis spans 364–494 and does not start at zero.
Measurement log — every subscribers count we have recorded
Measured (UTC)SubscribersChange
11 Sept 2026, 14:39479+67
3 Sept 2026, 22:18412+33
2 Sept 2026, 23:15379first reading

Engagement

20 posts held, back to 6 August 2026the reader has not yet reached the start of this channel’s public history, so older posts may sit further back, unread. Read across 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days
26.7%
avg views ÷ 479 subscribers
Avg views / post
128
13 posts measured
Reaction rate
this channel exposes no reaction counts
Posts in window
14
of 20 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.

What these figures were computed from
WindowRolling 30 days · latest post in window 2 September 2026
Posts held20 (6 August 20262 September 2026)
Views total1,661
Reactions total
Forwards / commentsnot exposed by the public surface — not measured, not estimated
Readings taken2 Sept 2026, 23: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.

Recent posts

1 Sept 2026, 17:41 UTC24 viewsread 2 September 2026
Forwarded from @hyphen_dev

🐽 امروز چندین پورت بخاطر اسپم های عمدی به صورت خودکار توسط سیستم موقتاً مسدود شدن. 🦠 توجیه مالک پورت ها برای رفع مسدودی هم اکثرا این بود که «پنل جواب نمیداده و برای همین تند تند زدیم.» 💬 بعد از چک ریکوئست ها و ریسپانس های پورت هاشون متوجه شدیم که تمام درخواست هایی که فرستادن سریعا و بدون تاخیر پاسخ دریافت کرده و این که «پنل کند بوده.» و یا «جواب نمیداد.» رو تکذیب میکنه. 👌 با اینکه میدونستم قصد خرابکاری داشتن اما پ

Signed Perseus

29 Aug 2026, 17:32 UTC90 viewsread 2 September 2026
Forwarded from @TAYGER_CH

https://t.me/+sYh6udn78mIzMmNk تو گپ در خدمت حضار هستیم.

Signed Perseus

25 Aug 2026, 22:01 UTC118 viewsread 2 September 2026
Forwarded from @TAYGER_CH

بیسیک اینو کامل دیباگ کردم لایبری جدید براش زدم بعدا براتون اونم پابلیک میکنم فایرو چنج بدید کامپ بگیرید هروقت هم خواستید آپدیتش بکنید خودتون

Signed Perseus

25 Aug 2026, 22:01 UTC112 viewsread 2 September 2026
Forwarded from @TAYGER_CHFile

فایرشو چنج زدم بیسیک کامپ گرفتم برای فایربیس Concurrency اضافه شد سرعت و پایداریش بالاتر رفته میتونید ازش استفاده بکنید، برای ادیت رت توی assets/sudoport.txt برید و پورت بزارید و smoke-domain سرچ بزنید دامین با Base64 انکریپت بزنید و جایگزین بکنید، برای پنل توی info.php توکن و عددی و اسم پورت بزارید. - @TAYGER_CH

Signed Perseus

24 Aug 2026, 08:41 UTC314 viewsread 2 September 2026

@eliothello وقتی پورت میخرید مثل آدم برید باهاش بتارید یا صبر کنید مشکلتون حل بشه نه اینکه بیاید پیوی اسپم و فحش بدید، پورت این بیناموس بچه سال هم اف شد کسی کیرشم دست این نده.

Signed Perseus

22 Aug 2026, 14:40 UTC132 viewsread 2 September 2026
Forwarded from @TAYGER_CHFile

گوگل اومده ورژن Safe Browsing آپدیت کرده دیگه آنتی بات های قدیمی کصشعرتون پچ میشن، یه آنتی بات دیگه زدیم پابلیک کردم براتون روی درگاهاتون ازش استفاده بکنید، توی فولدر Source میتونید سورس اصلی درگاهتون بزارید. header("Location: Source/"); اگرم توی سورس درگاهتون index.php یا index.html ندارید توی ریدایرکتر جلوی اسلش اسم فایل اصلی رو بنویسید که پیداش بکنه، البته خودش پیش‌فرض کار میکنه. - @TAYGER_CH

Signed Perseus

20 Aug 2026, 13:22 UTC151 viewsread 2 September 2026
Forwarded from @hyphen_devPhoto

🔄 Flood Auto retry ⏳ در حین انجام عملیات های جوینی، هرموقع هرکدوم از اکانت ها لیمیت‌جوین بشه، تایم محدودیت هرکدوم از اکانت ها بررسی میشه و برای تلاش مجدد همونقدر صبر میکنه. 🤚 همچنین دکمه توقف هم برای متوقف کردن ادامه تلاش ها وجود داره که با کلیک کردن روش دیگه جوینی در ادامه صورت نمیگیره. ⚙️ این آپشن از طریق پنل تنظیمات قابل فعالسازی/غیرفعالسازی هست. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

Signed Perseus

20 Aug 2026, 01:36 UTC104 viewsread 2 September 2026
Forwarded from @hyphen_dev

⬆️ آپدیت روی سرور ها اعمال شد. 🗂 مقدار فضای فایل منیجر از 50MB به 100MB تغییر پیدا کرد. 💬 مدیریت درخواست های همزمان تا ۳ برابر دقیق تر و سریع تر شد. 💬 کامنت خودکار از این به بعد با Typing… همراه میشه. 🛒 خرید پورت از طریق پورت سلر مجدد باز شد. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

Signed Perseus

19 Aug 2026, 20:51 UTC116 viewsread 2 September 2026
Forwarded from @hyphen_dev

〰️ امشب همراه با آپدیت، چند سرور جدید اضافه میشن و ظرفیت بیشتری در دسترس داریم. ✅ به محض آپدیت، خرید پورت های جدید مجدد قابل انجام میشه. 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

Signed Perseus

19 Aug 2026, 14:43 UTC116 viewsread 2 September 2026
Forwarded from @hyphen_dev

🧊 اگر ایده ای برای آپدیت های بعدی داشتید،(چه برای تلگرام و چه اپ های دیگه) حتما باهامون در میون بزارید. 😘 عجیب غریب بودن و یا سختیش مهم نیست، ایده با شما و عملی کردنش با ما. ⬇️⬇️⬇️

Signed Perseus

16 Aug 2026, 01:09 UTC141 viewsread 2 September 2026
Forwarded from @hyphen_dev

🐥 قراره هفته پر آپدیتی رو تجربه کنیم. 😊 از ابزار های مختلف تا بخش های جدید، همگی با بیشترین کیفیت و منصفانه ترین قیمت ممکن. 🤖 Link Bot ➡️@tabchi_port_bot 🧊 𝗛𝘆𝗽𝗵𝗲𝗻

Signed Perseus

Showing the 12 most recent of 20 posts we hold for @Sourcer_ch. 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

Republishes

Channels on the register whose posts this channel has forwarded.

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 11 September 2026 — this entry's latest reading, not the date you are reading this.

“Sourcer” (@Sourcer_ch), 479 subscribers as measured 11 September 2026. Telegram Register, tgregister.com/channel/Sourcer_ch.

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.