Channel

𝐃𝐎𝐌𝐈𝐍𝐀𝐓𝐎𝐑 𝐏𝐔𝐁𝐆

@IR_PUBG_SHAP

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

5,674subscribers

+100 since we began measuring on 2 September 2026

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

Register entry

Telegram ID	-1001816351749
Type	Channel
Username	@IR_PUBG_SHAP
Created	Between 1 October 2022 and 30 September 2023 — estimated from Telegram’s id allocation, not measured. How this range is calculated.
First recorded	2 September 2026
Last confirmed live	16 September 2026
Measurements held	5
Confirmed unchanged	1 time, most recently 16 September 2026
On Telegram	t.me/IR_PUBG_SHAP

Growth

5 measurements spanning 14 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 5,559–5,689 and does not start at zero.

Measurement log — every subscribers count we have recorded
Measured (UTC)	Subscribers	Change
16 Sept 2026, 15:20	5,674	+11
13 Sept 2026, 01:20	5,663	+89
8 Sept 2026, 19:20	5,574	-19
3 Sept 2026, 22:39	5,593	+19
2 Sept 2026, 18:32	5,574	first reading

Engagement

20 posts held, back to 31 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 1 page of Telegram’s post history, 20 posts per page.

ERR · 30 days: 0.278%; avg views ÷ 5,674 subscribers
Avg views / post: 15.8; 20 posts measured
Reaction rate: —; this channel exposes no reaction counts
Posts in window: 20; 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
Window	Rolling 30 days · latest post in window 2 September 2026
Posts held	20 (31 August 2026 – 2 September 2026)
Views total	316
Reactions total	—
Forwards / comments	not exposed by the public surface — not measured, not estimated
Readings taken	2 Sept 2026, 18:32 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

2 Sept 2026, 18:30 UTC2 viewsread 2 September 2026

5670272 123

2 Sept 2026, 18:28 UTC2 viewsread 2 September 2026

⭕️قابل توجه به دوستان عزیز ✅ ⚪️در صورت عضو نبودن در چنل اسپانسر به هیچ وج جایزه داده نمیشود🩸 🚀| @SevexGaming همین الان در کانال بالا عضو شید که بعدا پشیمون نشید 😠⚡

2 Sept 2026, 18:25 UTC8 viewsread 2 September 2026

2 Sept 2026, 18:20 UTC8 viewsread 2 September 2026

2 Sept 2026, 18:15 UTC5 viewsread 2 September 2026

2 Sept 2026, 17:45 UTC6 viewsread 2 September 2026

2 Sept 2026, 17:30 UTC4 viewsread 2 September 2026

2 Sept 2026, 16:30 UTC6 viewsread 2 September 2026

2 Sept 2026, 15:30 UTC9 viewsread 2 September 2026

2 Sept 2026, 11:15 UTC17 viewsread 2 September 2026

1 Sept 2026, 20:03 UTC20 viewsread 2 September 2026

😌𝗪𝗶𝗿𝗲𝗚𝘂𝗮𝗿𝗱 𝗣𝗨𝗕𝗚 وایرگارد پابجی موبایل🪙 🏳️𝗙𝗼𝗿 𝗔𝗹𝗹 𝗡𝗲𝘁𝘀 : 𝐢𝐑𝐚𝐍𝐂𝐞𝐋🛜 - 𝐌𝐜𝐢🛜 - 𝐑𝐢𝐓𝐞𝐋🛜 آیپی / سرور : امارات🇦🇪 📥Download WireGuard📤 ✅بهترین وایرگارد - صدر در صد تضمینی با پینگ پایین و ریجستر تیر فوق‌العاده👑 𝗙𝗼𝗿 𝗔𝗹𝗹 𝗗𝗲𝘃𝗶𝗰𝗲 : 𝐀𝐧𝐝𝐫𝐨𝐢𝐝🤖 - 𝐢𝐏𝐡𝐨𝐧𝐞🍏 - 𝐏𝐜💻 جهت حمایت از ما ریکشن مختلف و شیر کردن پست فراموش نشه😎

31 Aug 2026, 19:43 UTC30 viewsread 2 September 2026

Photo

⚠️رضایت وینر عزیزمون مبارکش باشه ✔️

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

Mentions

Named by 4 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.

PUBG_REX
@PUBG1_REX · 2,5288 posts 1SHOT
@PUBG_1SHOT · 3,1697 posts 𝐋𝐎𝐑𝐃 | کد دی ان اس و وایرگارد | DNS changer | wireguard
@PuBglLord · 2,6272 posts Sevex Gaming
@SevexGaming · 4271 post

Names

Channels on the register whose handles appear in this channel's posts.

کد دینس {پابجی موبایل}
@dns_kods · 11,04613 posts 𝗪𝗢𝗟𝗙 𝗖𝗢𝗡𝗙𝗜𝗡𝗚 🐺
@Npv_Tnnel · 4,96913 posts پابجی|𝐏𝐔𝐁𝐆 𝐓𝐈𝐆𝐄𝐑
@PUBG_TIGER1 · 10,51513 posts 𝟒𝐒𝐖𝐄𝐓𝐒
@PUBGMOILE4SWETS · 8,29413 posts قفل
@ROOM_TIGER · 2413 posts 𝐒𝐎𝐋𝐈𝐂𝐎 𝐏𝐔𝐁𝐆𝐌
@SoLiCo_pubgm · 3,69113 posts 𝚃𝙰𝙼𝚈 𝙲𝙻𝙾𝚂𝙴
@TAMY_Close2 · 6,68713 posts X6 ROOM
@X6_ROOM · 24113 posts Sevex Gaming
@SevexGaming · 4279 posts PUBG_REX
@PUBG1_REX · 2,5288 posts 1SHOT
@PUBG_1SHOT · 3,1698 posts 𝗷𝗮𝘃𝗮𝗱𝗶_𝗽𝗹️️𝟰𝘆
@javadi_pl4y1388 · 1,3566 posts 𝚄𝙵 - 𝚃𝙴𝙰𝙼 ¦ 𝙲𝙷𝙰𝙽𝙽𝙴𝙻
@UF_TEAM1 · 1,5886 posts HyperConnect
@Hyper_Connect10 · 2725 posts 𝐋𝐎𝐑𝐃 | کد دی ان اس و وایرگارد | DNS changer | wireguard
@PuBglLord · 2,6275 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 September 2026 — this entry's latest reading, not the date you are reading this.

“𝐃𝐎𝐌𝐈𝐍𝐀𝐓𝐎𝐑 𝐏𝐔𝐁𝐆” (@IR_PUBG_SHAP), 5,674 subscribers as measured 16 September 2026. Telegram Register, tgregister.com/channel/IR_PUBG_SHAP.

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.