Telegram RegisterThe public register of Telegram
Telegram profile photo for Pace Acc Receiver

Channel

Pace Acc Receiver

@Pace_Receiver

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

11,048subscribers

-4 since we began measuring on 7 August 2026

Risers and fallers across the register · movement among entries of 10,000–31,623.

Register entry

Telegram ID-1002392031383
TypeChannel
Username@Pace_Receiver
Created13 April 2025measured — dated from the channel’s first post
First recorded7 August 2026
Last confirmed live1 September 2026
Measurements held22
Confirmed unchanged1 time, most recently 1 September 2026
On Telegramt.me/Pace_Receiver

Growth

11,00811,06211,0357 August 2026 — 11,052 subscribers8 August 2026 — 11,050 subscribers9 August 2026 — 11,051 subscribers10 August 2026 — 11,043 subscribers11 August 2026 — 11,039 subscribers12 August 2026 — 11,024 subscribers14 August 2026 — 11,021 subscribers15 August 2026 — 11,016 subscribers16 August 2026 — 11,015 subscribers17 August 2026 — 11,012 subscribers18 August 2026 — 11,009 subscribers19 August 2026 — 11,008 subscribers21 August 2026 — 11,013 subscribers23 August 2026 — 11,056 subscribers25 August 2026 — 11,051 subscribers26 August 2026 — 11,057 subscribers27 August 2026 — 11,058 subscribers27 August 2026 — 11,062 subscribers29 August 2026 — 11,060 subscribers30 August 2026 — 11,059 subscribers31 August 2026 — 11,057 subscribers1 September 2026 — 11,048 subscribers11,0487 August 20261 September 2026
22 measurements spanning 24 days, net -4. 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 11,000–11,070 and does not start at zero.
Measurement log — every subscribers count we have recorded, most recent 20 of 22
Measured (UTC)SubscribersChange
1 Sept 2026, 01:1711,048-9
31 Aug 2026, 03:0711,057-2
30 Aug 2026, 01:2411,059-1
29 Aug 2026, 03:1511,060-2
27 Aug 2026, 23:4311,062+4
27 Aug 2026, 00:5611,058+1
26 Aug 2026, 01:3811,057+6
25 Aug 2026, 01:5311,051-5
23 Aug 2026, 14:4211,056+43
21 Aug 2026, 23:4611,013+5
19 Aug 2026, 18:5311,008-1
18 Aug 2026, 21:4711,009-3
17 Aug 2026, 23:1311,012-3
16 Aug 2026, 21:5711,015-1
15 Aug 2026, 16:2511,016-5
14 Aug 2026, 01:5611,021-3
12 Aug 2026, 18:4511,024-15
11 Aug 2026, 15:4211,039-4
10 Aug 2026, 14:0811,043-8
9 Aug 2026, 14:1511,051first reading

Engagement

7 posts held, back to 13 April 2025the reader has reached the start of this channel’s public history, so this is the full archive Telegram still exposes. Read across 37 pages of Telegram’s post history, 20 posts per page.

Nothing published in the last 30 days. ERR and ER are rolling 30-day measures, so there is nothing to compute — we hold 7 posts for this entry, the most recent from 26 August 2025. An engagement rate over an empty window would be a number about nothing.

Reaction mix

2,526 reactions across 5 posts, in 18 distinct kinds. The most used accounts for 40.3% of them.

Every reaction kind recorded on the sample, most used first
ReactionCountShareShare, drawn
1,01840.3%
👍77630.7%
🔥1526.02%
🥰1395.50%
👏793.13%
😁793.13%
👎652.57%
🖕642.53%
🤬401.58%
💔391.54%
🤨291.15%
🤔160.633%
🤓150.594%
🤣90.356%
😍30.119%
👌10.04%
🙏10.04%
🤝10.04%

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 5 of the 7 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 2,526 reactions in total: the kind of figure the paragraph above means by “a reaction total printed elsewhere on the page”.

Measured over the 7 most recent posts we hold, published 13 April 2025 to 26 August 2025, using the newest reading held for each. Telegram Stars are excluded: they are a payment, not a reaction, and they have their own section.

Recent posts

26 Aug 2025, 22:51 UTCviews —

Pace Acc Receiver pinned «کاربران گرامی توجه داشته باشید برای استفاده از ربات عضویت در کانال اطلاع رسانی الزامی است. ❗️ https://t.me/+LCkw_P2y8Xg3OThk در صورتی که درخواست عضویت شما تایید نشده است به پشتیبانی مجموعه اطلاع دهید. ❗️ @Pace_Acc_Sup Dear users, please note that membership…»

29 Apr 2025, 07:41 UTC≈58,200 views1,361 reactionsread 29 August 2026

کاربران گرامی توجه داشته باشید برای استفاده از ربات عضویت در کانال اطلاع رسانی الزامی است. ❗️ https://t.me/+LCkw_P2y8Xg3OThk در صورتی که درخواست عضویت شما تایید نشده است به پشتیبانی مجموعه اطلاع دهید. ❗️ @Pace_Acc_Sup Dear users, please note that membership in the notification channel is required to use the bot. ❗️ https://t.me/+LCkw_P2y8Xg3OThk If your membership request is not approved, please inform the supp

👍466423🥰118🔥75🖕53😁48👎41🤬40

21 Apr 2025, 16:37 UTC≈54,000 views326 reactionsread 29 August 2026

کاربران گرامی توجه داشته باشید برای استفاده از ربات عضویت در کانال اطلاع رسانی الزامی است. ❗️ https://t.me/+LCkw_P2y8Xg3OThk در صورتی که درخواست عضویت شما تایید نشده است به پشتیبانی مجموعه اطلاع دهید. ❗️ @Pace_Acc_Sup Dear users, please note that membership in the notification channel is required to use the bot. ❗️ https://t.me/+LCkw_P2y8Xg3OThk If your membership request is not approved, please inform the supp

186👍71🔥26👎18🖕11🥰6👏5🤝1

16 Apr 2025, 15:41 UTC≈42,000 views290 reactionsread 29 August 2026

برای جلوگیری از ورود افراد ناشناس یا مشکوک، عضویت برخی اکانت‌ها ممکن است تایید نشود⚠️ در صورتی که یکی از اعضای تیم شما موفق به عضویت در کانال نشده، لطفا لیستی کامل از اعضای خود را آماده کرده و برای پشتیبانی ارسال نمایید✅ همچنین حتما پیش از ارائه آیدی، مطمئن شوید که فرد مورد نظر قبلاً در تیم شما فعالیت داشته و آمار ارسال کرده باشد❗️ از همراهی و همکاری شما سپاسگزاریم. 🤖 @Pace_Acc_Sup

167👍57😁24🤓15🥰15🔥12

14 Apr 2025, 19:05 UTC≈39,100 views302 reactionsread 29 August 2026

کاربران گرامی توجه داشته باشید برای استفاده از ربات عضویت در کانال اطلاع رسانی الزامی است. ❗️ https://t.me/+LCkw_P2y8Xg3OThk در صورتی که درخواست عضویت شما تایید نشده است به پشتیبانی مجموعه اطلاع دهید. ❗️ @Pace_Acc_Sup Dear users, please note that membership in the notification channel is required to use the bot. ❗️ https://t.me/+LCkw_P2y8Xg3OThk If your membership request is not approved, please inform the supp

👍127118🤔16👏12🤣9😁7👎6🔥4

13 Apr 2025, 22:18 UTC≈25,300 views247 reactionsread 29 August 2026

برای عضو شدن در چنل اطلاع رسانی خرید های تیم پیس با استفاده از لینک زیر درخواست بدید https://t.me/+LCkw_P2y8Xg3OThk

124👍55🔥35👏33

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

Citation-graph rank

Citation-graph rank — 1,139,914 of 1,629,452 entries in the measured graph. A weighted position computed from the forward and mention edges below — republished posts weigh more than named mentions — and recomputed periodically, over the whole graph. Published only as this ordinal position, never as a score: a position is a fact, and a score printed beside one channel’s name would read as a verdict this register does not make. The two counts beneath stay separate for the same reason mentions are never summed with forwards anywhere else on this page — a named-by count costs nothing to manufacture. The top 100 by this measure, or how it is computed.

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.

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

“Pace Acc Receiver” (@Pace_Receiver), 11,048 subscribers as measured 1 September 2026. Telegram Register, tgregister.com/channel/Pace_Receiver.

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.